A Service Design Principle for better reports
It's now a few times I've used the same structure for a few research projects. I basically separate the report into four buckets:
- A summary
- Simple questions with simple answers
- Complex questions with complex answers
- Details (methodology, research question, etc.)
This helps me show where decisions can be taken really easily as the answers are clear and where the decision-making still needs a bit more reflection.
I think that separating the simple from the complex stuff is something that is a structure that we can also use for other moments when we share pieces of information. For example, when you share a new policy about remote work in your organisation, you can do that too. This would help employees see which are the hard lines that are now clear, and what are things where things need further discussion.
Action question
How can you structure the information you share so that it helps separate clearly what's clear and what needs to be discussed further?
Daniele's note