Stop writing Assumptions

Assumptions seems to be everywhere; in proposals, solution documents, project schedules... 

And it is not common to hear from Management “we need to have some more assumptions around that, please add..”..

It is time to stop writing assumption.

Why?

Because Assumptions brings uncertainty, it open interpretation, and it fosters a bad “I told you already, so not my responsibility” attitude.

None of which drives collaboration and design thinking into Solutions or Agile methods into Planning

If no Assumptions then what?

Instead of writing a long list of more or less relevant Assumptions, put your effort into what truly bring value. Which is analyzing and designing the best solution, the best complete proposal or the most realistic schedule.

Focus should be on ensuring you really understand the problem the solution is going to resolve. 

Then with an open mind and Design Thinking sessions come up with the best solution to the problem.

 If not list of Assumption, then what?

• Write clearly what your solution will do and why this is the best solution design
• Write what your solution can NOT do in case there is functionality or constraints. And if possible elaborate why the solution cannot or will not include this.
• For uncertainties write them as possible Risks and provide an initial impact assessment so it is clear that if this happens then the impact will be this.

 Put yourself in the readers position

Put yourself in the readers position. What will provide the reader with the best understanding and confidence level when reading your documents?

List of more or less relevant assumptions which you likely will have to debate the understanding of,f in case of a difference in expectation or dispute?

OR

Clear description of the solution what and why and what it will not, including a list of potential Risks with impact to the project or solution.

Sounds like more work?

It might cause a little more work but it will force the team to go through a proper analysis process and actually think the solution end-to-end, and not just make a quick assumption.

We don’t have time to do this

Time is of the essence in every job. But if there is not time to do a proper end-to-end solution design,  then perhaps the solution should not be proposed at all