Workflow from planning to design

ArticleDirectory

• Phase 1
• 2. creative stage
• Three Stages
• 4. Correction phase

Move it! Move PM & UE--"Workflow from planning to design"

The title sounds a little frustrated. In fact, what I want to express is to allow more interaction between PM and UE, so that everyone can work more in a complete process.Clear,Efficient,Joy!

First look at the directory:

• A story of Part1 introduces the environment of PM & ue cooperation
• Problems and Solutions of the current process of Part2
• Part3 workflow node outline

Before starting the discussion, I want to tell a story.

Previously, PM planned to build a cross-sea bridge with ue. PM was the first to start from the east coast to the central sea.

Repair, repair, PM completed half of the bridge, and then shouted at the UE in the West Bank across the fog-filled strait:

"Hello ~~ I have fixed this half ~~~ Start repairing the other half ~~~~ How can this problem be solved ~~~~ The bridge will be open to traffic in N days !"

Then, ue began to repair, braved the heavy fog, worked overtime for N days, and then after N days ......

Misaligned ......

I have been working hard for several days. When I see such a scene, both PM and UE will secretly scold me ~

* The above stories may be extreme or exaggerated in order to make a dramatic effect. They only represent the feelings of individual stages. PM & ue do not mind.

However, I think this story can clearly depict some of our typical workflows:

Step 1. PM planning requirement document + line chart ------------ (PM repairs half of its own bridge)

Step 2. Submit it to UE for simple communication and confirm the schedule ------------ (shouting to ue across the Channel)

Step 3. Ue immersed in the production page ---------------- (UE immersed in repairing his half)

Step 4. Send the page to PM ---------------- (N days later... acceptance... The two sides are not aligned ....)

Step 5. Modify, send it to PM, modify it, and complete ------------- (the rework of potholes)

This process has some problems.

Problem 1 is not clear enough-- Insufficient communication

"When the bridge was being repaired, there was heavy fog at sea, so we had to work hard and communicate too little ."

---- PM & UE is basically a Black Box job. The planning process of PM is invisible to ue, and the design concept of UE is unknown to PM. As a result, at the moment of acceptance, all the problems of poor communication are always exposed.

"PM has already completed half of the bridge and let ue intervene. After that, there are no clear nodes to ensure that the bridge has not been repaired ."

---- The process is relatively simple and crude, and there are no clear steps and nodes. UE has been passively working in chaos.

Problem 2 is not efficient enough

Poor communication eventually leads to the inconsistency between the PM expectation and the design draft during acceptance. Or, the modification or disruptive modification may be delayed.

After the PM bridge is repaired, it will be difficult for the UE to build the bridge.

Question 3 is not fun

The result of "taking the heavy fog" work + "groose" should not be a good emotional experience.

So what should we do? -- PRINCIPLES OF SOLUTIONS

How to be clear and efficient

· Principle 1:Advance Communication

Before starting the bridge construction, PM & ue communicated in advance, and UE raised his own concerns. ue also had a better understanding of PM's planning ideas, rather than notifying ue after PM's half was built, in this way, the UE is well prepared.

· Principle 2:Simplified requirements

From the beginning, streamline the demand control scope (whether the bridge is compatible with cars, trains, and bicycles), and use the unanimously recognized targets to filter out meaningless trial solutions.

· Principle 3:Segmented confirmation

Formulate a clear "project stage" and use "segmented validation" to control errors. If the PM & UE can divide the process into several validation points during the bridge construction, and regularly look at each other, there will be no very different results for the moment.

· Principle 4:Full Communication

Keep active communication throughout the entire process of small steps and run fast, so that we can see where the "zombie" comes from and where the "pea" is like?

How happy

Think together: The idea itself needs a relaxed and pleasant atmosphere as the foundation to inspire, such as brainstorming, and it will also produce more relaxed and pleasant feelings.

Organization photo: Taking a photo is a souvenir of your work.

After talking about the principle of solution, the focus is on

Phase 1

Background

Discussion Objectives and scope

Confirm target

2. creative stage

Concept

Evaluation concept + proposal

Validation Concept

Three Stages

Validation policies and functions

Confirm feeling

Confirm text (slogan)

Validation line diagram

Confirm Layout

Confirm atmosphere

4. Correction phase

Comments

Modify Iteration

Complete

Confirm online results

 

Due to the length, it is inconvenient to elaborate on each node. Only a few key nodes are described:

• [Understanding the background] in the phase, we should clarify who is the "decision maker" and get the "decision maker" approval in the [goal] [concept of confirmation.
• All people's ideas should be put forward at the beginning, rather than just talking about them.
• The Goals previously recognized are used as the criteria for ruling, rather than the personal preferences of "decision makers.
• [Creative stage] is a stage full of fun and challenges, and we often skip to [production stage]
• The strange thing is that the [idea stage] is sometimes controlled by the PM, and sometimes the PM will intentionally kick the UE (maybe it cannot be thought out, or it is too hard to think about ), the solution is to create ideas together ~
• [Confirm online results] ensures that previous efforts are not distorted after they are launched.

Thoughts on the workflow itself:

A process is not a constraint, but a guide.

Do not be intimidated by the above series of nodes. It takes a lot of time to complete them one by one. In fact, many nodes can be merged and completed in one communication.

The process is like a memorandum, reminding us not to miss out and do some important things.

The process is more like a travel bag list, reminding us what to bring and there are different levels of travel bag list "packages" based on the travel level ", for example, if you want to take your wallet, key, mobile phone, and badge to your company, you need more travel bag lists in Tibet, such as medicines and down jackets. If you ignore the importance of the "bag List" (workflow) and forget to bring a down jacket when you leave, your trip to Tibet will surely be a trembling journey.

Similarly, we also need to use different "bag list" packages based on different levels and urgency cases.

Another role of the process is to efficiently coordinate the PM & ue time and optimize the order of work. For example, in the [production phase], if the PM content module still needs time to be determined, you only need to confirm the [confirmation feeling] [Validation slogan] Step, UE can design the overall atmosphere.

Source Address: http://xdc.baidu.com /? P = 643