A Good Brief Saves Time and Money
The quality of the software you receive is directly related to the quality of the brief you provide. A clear brief means fewer misunderstandings, fewer revisions and a faster delivery. Here is what to include and how to communicate your requirements effectively.
Start With the Problem, Not the Solution
Instead of saying I need a database with 15 fields and 3 user types, start with our compliance tracking spreadsheet is unreliable, 3 people need to update it simultaneously, and we miss expiry dates because there are no automatic reminders. The problem description helps the developer understand your actual needs and often leads to a better solution than a prescriptive specification.
Show Your Current Process
The most valuable thing you can share is your current spreadsheet, paper form or manual process. Screenshots, example data (anonymised if needed) and a walkthrough of how you currently do things tells a developer more than any written specification. If you are replacing a spreadsheet, share it. If you are digitising a paper form, photograph it.
Define Your Users
Who will use the system? How many of them? What are their different needs? A manager who needs overview reports has different requirements from a team member who needs to enter data quickly. Defining your users early helps shape the interface and permissions model.
Prioritise Ruthlessly
Separate your requirements into must-have (the system is useless without these), should-have (important but could be added later) and nice-to-have (only if time and budget allow). This helps the developer deliver the most valuable functionality first and manage scope effectively.
Do Not Worry About Technical Details
You do not need to specify the programming language, database type or hosting platform. That is the developer's job. Focus on what the system needs to do, not how it should be built. A good developer will recommend the best technical approach based on your requirements.
Ready to Brief a Project
If you have a process you want to digitise or a spreadsheet you want to replace, get in touch and I will help you shape the brief. I ask the right questions to ensure we build the right thing.
Got a Spreadsheet That's Driving You Mad?
Send it over — I'll tell you what an app version would look like and what it'd cost. No obligation.