A new product.
Clarify who the product is for, what people need to do and which features belong in the first stage.
Product design & technical planning
Make the important decisions clear before development.
We turn broad requirements into priorities, user journeys, interface designs and a technical plan. Planning can be a focused first stage for a new product, an improvement or a system migration.
A plan for the next stage
Product brief
- Goals
- Users
- Priorities
User journey
- Start→
- Key task→
- Outcome
Technical direction
Interface↔Services & data
Where we can help
Start with the decisions your product needs.
An existing product.
Review the journeys, interfaces and system constraints around a planned improvement, extension or migration.
A defined part of the work.
Plan a specific interface, workflow or integration before deciding how to implement it.
Inside the planning materials
Useful materials help you make a decision.
These illustrative extracts show the purpose of planning outputs. The actual documents and level of detail depend on the agreed stage.
Planning scope
What the planning can include.
Requirements and priorities.
Identify the users, business goals, constraints and first-stage features. Clarify what is included and what can follow later.
User journeys and prototypes.
Map the main tasks, screen flows and important states. Use wireframes or an interactive prototype where they help review the experience.
Interface design.
Define the layouts, content and interactions needed for the agreed screens, including the relevant desktop and mobile views.
Architecture and integrations.
Plan how interfaces, data and services connect. Review existing systems and available interfaces before recommending a technical direction.
Delivery and handover planning.
Define implementation stages, review points, dependencies and the materials needed for the next stage of work.
Deliverables & handover
Clear scope. Useful materials. A practical next step.
We agree which decisions and materials the planning stage needs to cover. A focused review and a broader design phase can have different deliverables; the scope defines the level of detail.
Requirements and journey records.
Agreed priorities, scope boundaries, user flows and the assumptions or questions that still need to be resolved.
Design and prototype materials.
Wireframes, interface designs or an interactive prototype where included, with notes on the agreed behaviour.
Technical direction and delivery stages.
The proposed system relationships, integration requirements, implementation stages and handover notes included in the scope.
Starting information
A short overview is enough to begin.
You do not need a finished specification or a technology choice before contacting us. Start with the business need and what you already know. We can agree confidentiality and access arrangements before sensitive information is shared.
The people who will use the product and the tasks it should support.
Any existing product links, sketches, designs or requirements.
The systems, integrations or operating constraints already in place.
Any budget range, target dates or priorities that will shape the first stage.
How will we work together?
See how we review progress, handle feedback and changes, and plan release and handover.
An applied example
Map the handovers from booking to completion.
Use the customer, office and field team roles to define the business rules and one complete journey for a useful first stage.
Before you decide
Make the next decision with more clarity.
Does your business need an app or a web application?
Start with the people doing the work, where they do it and how often they return. The right interface follows the task, rather than a preferred technology.
What shapes a software project's cost and timeline?
A list of screens is a starting point. A useful estimate also needs the behaviour, data, dependencies and delivery work behind those screens.
Practical questions
Before a planning stage
Can we commission planning without committing to development?
Yes. Planning can be a separately agreed stage. We define its scope and materials first, and discuss any later development as a separate next step.
Can we start with an idea rather than a specification?
Yes. A brief description of the users, business need and main tasks is a useful starting point. Part of planning is deciding what needs to be clarified before implementation.
Is an interactive prototype a finished app or website?
A prototype helps review flows and interactions. Production development, backend services, testing and deployment are separately defined work. We agree what the prototype needs to demonstrate.
Will planning establish the development cost and timeline?
It helps make estimates more informed by clarifying scope, dependencies and stages. Costs and timing are discussed around the proposed implementation, with remaining assumptions and further assessment identified.
Let’s start a conversation
Which product decision needs clarity?
Share the idea, the users and the questions you need to settle before development.
Phone+61 432 712 222
Melbourne addressSuite 1208, 530 Little Collins Street
Melbourne, VIC 3000, Australia
Melbourne, VIC 3000, Australia