flyingpenguinSOFTWARE
All software guides

What to bring to a software conversation

You do not need a technical specification before speaking to me. A clear example of the work you do now gives us somewhere useful to start.

Pick a job you know well.

Choose one task and explain it from start to finish. Who starts it? What information comes in? What gets checked? What tells you it is finished? A real sequence makes the missing pieces easier to spot.

Show the tools involved.

List the spreadsheets, websites and business systems used along the way. Say who owns the accounts and what information moves between them. Start with descriptions or redacted examples; do not send passwords or customer records in an initial enquiry.

Explain the exceptions.

The unusual cases often shape the software. A booking that needs approval, an order with missing information or a task that changes hands all deserve a place in the conversation.

Name the first useful release.

What complete job would make the first version worth using? Separate that from later ideas. We can turn the agreed journey into prototype screens, checks and a written scope.

Show me the bit
that slows you down.

A task, a spreadsheet or an idea you want to work through. Describe it first and we can agree what to look at next.

Tell me about the jobOr book a short call