The document outlines a seven-step process for building a process for work projects. It discusses reviewing existing processes, identifying good, bad, and ugly aspects, planning the new process on a board for discussion, integrating it into internal systems, getting client and team feedback, and regularly reviewing the process for improvements. The company applied this seven-step process to develop a new process for their web projects which has resulted in benefits like whole team buy-in, meeting client expectations, easier transitions back to work, quicker sign-offs, coverage for absences, positive client feedback, and space for creativity.

1. Got work to do?
We did a process.
We applied it to our new web projects.
Here are seven simple steps to building a process for your work.

2. Why should we have
a process?
The whole team has buy in. Client expectations are met.
Start - stop work is easier to jump back into. Sign offs are definitive and quicker.
Anyone can jump in when absences happen. Feedback from clients has been very positive.
It gives us space to be creative within projects. It gives us something to rely on.

3. 1. Review
Review your existing process or work. Figure out
what causes stress or friction.

4. This was our existing process. It needed a little work
to get in shape for new projects.

5. 2. GBU
GOOD. BAD. UGLY.

6. Based on previous project experience we defined a list of what was Good,
Bad and Ugly. This informed our major and minor changes to the process.
Clients are very happy :)
We are delivering on time.
We are delivering great DM
results.
We’ve built new functions.
Over budget on one project. Incorrect content migration time.
Minimal marketing integration. No asset creation time allocated.
Spent too long on internal meetings.
Development team have
learned new skills.

7. 3. Plan it on a
board
We had a couple of meetings and put the process on the wall. We discussed
every element. Having it as a physical item on the wall gave us a focal point to
talk about.

10. 4. Feed into your
systems.
We use Basecamp here at Zest. If you have internal systems
you can migrate your process from the wall into your tools.

11. 5. Involve the
client
We asked the client for feedback on the process. Their
input was very useful and it informed many of our updates.

12. We got some really good feedback from our clients. There
is always room for improvement but it was a great start.

13. 6. Involve the
team
We showed the wider team our process and asked
for their input. This was VERY valuable.

14. 7. Review regularly
Our process is not perfect. We have a GBU meeting after
each piece of work we do to see if we can improve.