Accountability is a two-way street. When you have committed to what you will do and I have committed to what I will do we are able to hold each other accountable for what we have to do. So far so good. But if we leave it till the end of the task to follow up we may find we have unwanted surprises for each other. Here is a tool we used in projects manage this subtle but dangerous problem. This approach was explained to me by the eclectic Di Joseph who smoked like a chimney, had Cape Chameleons in her garden and only ever ate winegums three at a time starting (and this is really really important) starting from the green side. Always the green side.
For accountability, consider splitting project tasks. This quality view of the work provides a way for teams to coordinate what they will deliver.
- 0% duration: At the start of the task the work is handed to the responsible person.
- 10% duration: At ten percent of the duration of the task the person responsible for delivery holds a little workshop to explain to a select group of stakeholders how they intend to go about creating and delivering the product. All attending give their input.
The responsible person gets on with the job. At this point anyone managing the work should consider the delegation issues.
- 50% duration: At half-way through the task the responsible person or team should be 80% complete. They present their deliverable for a quality review to a group of stakeholders. For high impact deliverables this should be a Formal Technical Review.
The responsible person collects all the input they get in the review and they put in the work to complete the product, along with the suggested changes.
- 80% duration: Prior to completion of the task, the deliverable should be 100% complete. The responsible person holds a final review in which the customer for the deliverable and other stakeholders evaluate the delivery. Final quality issues are raised.
The responsible person puts in the final touches where necessary.
- 100% duration: The task is now complete. The responsible has the deliverable signed off by the customer for the deliverable and the manager (if there is one) of the task.
Accountability in teams requires a way to see shades of grey. This tool will allow you to categorise your delivery within these shades.
