How to guide technical people
For the rest of us, non-technical people
One of the biggest barriers is to communicate what you have in your mind for them to create it accurately.
Here’s the best way to communicate your requirements clearly:
Start with why. Give the context and the reason
What output do you need
How you need it. How do you want to use or view it
Describe the audience. The ‘who’ tells us a lot about what to build.
The best way to give technical clarity for any aspect is:
What goes in (data, inputs, forms, etc.)
What happens to it (calculations, etc. Is optional)
What comes out (reports, dashboards, summaries, etc.)
How you want to see it (what charts, views, etc.)
It’s best to write all this, as it’s easy to communicate it, keep track of and fill in any blanks later on. You won’t have to keep repeating things all the time.
Incidentally, this works better for the tech guys also.