Discovery Workshop
One or two days taking your idea apart, before anyone writes code.
- On site
- Remote
- Full day
How it works
We come to you or we do it remotely; that changes little about the day. It does not start with a presentation from us but with a question to you: what happens today when someone does the thing the software is supposed to do later?
Morning, how it works now
You walk us through today’s process, step by step, with the real tools. Where it snags, where people improvise, which spreadsheet is actually holding the whole thing together. This takes longer than anyone expects, and most requirements come out of it.
Afternoon, what the software has to do
Now we turn it around. We collect what the result has to achieve and sort it straight away into three piles: the core, the later, the unnecessary. The third pile matters most and is the least popular.
The uncomfortable questions
We ask about the things conversations tend to steer around. Who decides when you disagree? What happens if this takes twice as long? Is there anyone in the building who is against it? These answers cost nothing and save weeks.
The second day
If there is one, it belongs to specifics. We sketch the main flows on paper and walk through them — not as design, but to check whether we understood you correctly.
- Someone who can decide on budget. Without them, every second question gets deferred.
- Someone who knows the daily work the software is meant to replace — not only management.
- Access to what is in use today: spreadsheets, legacy system, paper trail.
A record of what should be built, what is deliberately left out, and the questions that stayed open.
If you skip this
Without the workshop we build on assumptions. Most of them hold. The two that do not surface once the software is finished — and by then the correction is no longer a conversation, it is a rebuild.
Questions about this step?
A conversation costs nothing and takes half an hour. Afterwards you will know whether we are a fit.