Work flow from planning to design: clear, efficient, joyful

Article Description: work flow from planning to design.

Welcome everyone to XDC! The subject we are discussing this time is:

Move it! Pm&ue Move--"from planning to design workflow"

The title sounds a bit lame, in fact, I want to express the meaning is to let pm&ue more interaction between, so that everyone in a perfect process to work more clear, efficient, happy !

First look at the table of contents:

Part1 A story leads to the dilemma of Pm&ue cooperation

Part2 current process problems and resolution principles

PART3 Work Process Node outline

PART1 A story leads to the dilemma of Pm&ue cooperation

Before I begin to discuss the process, I want to tell a story first.

Once upon a time, PM intended to combine the UE to repair a sea-crossing bridge. PM takes the lead from the east Coast to the sea central repair.

Repair, the PM completed half of the bridge, and then across the foggy Channel, the West Coast UE shouted:

"Hey, my half has been repaired, you start to repair the other half, add strength Ah, n days to open the bridge to traffic Oh!" ”

Then, the UE began to repair, braved the heavy fog to repair, overtime n days of the class, and then N days after ...

It's crooked.

Hard work for several days, see such a scene whether the PM or UE will curse the pit dad ~

* The above story for the dramatic effect may be somewhat extreme and exaggerated, representing only the individual stage feelings. PM & UE Students please don't mind.

But I think this story can be a more vivid description of some of our typical work flow:

Step 1. PM Planning Requirements Document + Wireframe —————————————— (PM repair half of the bridge)

Step 2. To UE simple communication to confirm the scheduling ———————————— (across the channel to the UE shouted)

Step 3. UE immersed in the production page —————————————————— (UE bury himself in the half)

Step 4. Finish the page to PM —————————————————— (n days later ...) The two sides are not aligned .... ）

Step 5. Revise, send PM, revise, finish ——————————————— (Pit Dad rework)

There are some problems with such a process.

Problems in PART2 and their solving principles

Question one not clear enough--communication is not sufficient

"When the bridge was repaired, there was a heavy fog at the sea, and everyone was hard at it, communicating too little. ”

Pm&ue is basically a line of work, black box homework. PM's planning process UE is not visible, UE design ideas pm do not know. So in the acceptance of the moment, all the bad communication problems in the total explosion.

"PM has completed half of the bridge before UE is involved, and thereafter there is no definite node to make sure the bridge is not crooked." ”

The process is simpler and more brutal, with no clear steps and nodes. The UE has been working passively in chaos.

Problem two is not efficient

Poor communication ultimately lead to the acceptance of PM expectations and design draft is not compatible. Or simply diametrically opposed to change, disruptive modification, delay scheduling.

PM Bridge after the repair and changes, will lead to the UE building a bridge is very embarrassing difficulties.

Question three not happy enough

"The Fog" work + "pit Dad" results should not be a good emotional experience

So what do we do? --The principle of solution

How to be clear + efficient

Principle one: communicate in advance

Beginning to repair the bridge, Pm&ue Advance communication, UE raised their concerns, UE also better understand PM planning ideas, rather than pm their half built, only to inform the UE, so the UE is ready.

Principle two: streamlining demand

From the beginning to streamline the scope of demand control (bridge should not be car, train, bike compatible), with the unanimous approval of the goal to screen out meaningless attempts to plan.

Principle III: Subparagraph confirmed

Establish a clear "project phase" with "phased confirmation" to control errors. If you repair the bridge Pm&ue can divide the process into several confirmation points, a regular look at each other, there will be no docking of the moment very different results.

Principle IV: full communication

Keep the whole small step of the active communication, time to disperse the fog, so that we can see the "zombie" from Where, "peas" where the species?

How to be happy

Think of ideas together: The idea itself requires a relaxing atmosphere for inspiration, such as brainstorming, and more relaxed and enjoyable feelings in the process.

Organization Photo: The photo itself is a souvenir for their own work, fun.

That's the point.

PART3 Work Process Node outline

One start-up phase

Understanding the background

Discussion objectives, scope

Confirm Target

Two creative Stages

Produce Concepts

Concept of assessment + proposal

Confirmation concept

Three production stages

Confirm Policies, features

Confirm Feeling

Confirmation Copy (slogan)

Confirm Line Block Diagram

Confirm Layout

Confirmation atmosphere

Four revision stages

Assessment of a draft

modifying iterations

Complete

Confirm the online effect

Due to space reasons, each node is inconvenient to start in detail, just say a few key nodes:

In the "Understanding the background" phase, be clear about who is the "decision maker" and get "decision maker" approval when you "confirm the goal" and "confirm the concept."

Everyone's ideas should be put forward in the first, not halfway.

Use previously recognized "goals" as the criteria for adjudication, rather than "decision makers" of personal preferences.

"Creative phase" is a fun and challenging stage, and we often muddle through, jump directly to the "production phase"

The strange thing is that the "creative phase" is sometimes firmly controlled by PM, sometimes pm will deliberately kick to the UE (may be think not to come out, or too lazy to think), the solution is everyone together to creative ~

"Confirm the online effect" can ensure that previous efforts on the line will not deform.

Thinking about the workflow itself:

A process is not a constraint, but a boot.

Do not be intimidated by the chain of nodes above, thinking that it will take a lot of time to complete, in fact, many nodes can be merged in a communication completed.

The process is like a memo that reminds us not to miss out on something important.

The process is more like a travel baggage list, remind us what to bring, and according to the level of travel, there are different levels of luggage list "package", such as to go to the company as long as the wallet key \ Phone cards, and go to Tibet's luggage list will be more, such as medicine \ down jacket. If you ignore the importance of the "baggage List" (workflow) and forget to take your down jacket when you leave, your trip to Tibet is bound to be a shiver.

Similarly, depending on the level and urgency of the case, we also need to use a different "pack list" package

Another function of the process is to efficiently co-ordinate pm&ue time and optimize the order of things. For example, if the PM's content module still needs to be determined in the "production phase", then the UE can conceive the overall design of the atmosphere as long as the "confirm Feeling" "Confirm slogan" step is identified.

The above is only a personal opinion, pending the practice of continuous revision, but also look forward to your corrections and suggestions.