Define
Identify users, the problem and the important workflows. Discuss constraints, success criteria and what belongs in the first release.
Make the decisions.
Then make it work.
A practical engagement connects the product problem to the scope, implementation and responsibilities after release.
Design & engineer
Shape the experience and architecture together. Build in increments that can be reviewed against the agreed product scope.
Release & hand over
Prepare deployment and distribution, check the critical journeys and agree documentation, ownership and ongoing support.
Founder-led.
Directly accountable.
Axis Innovation Group is a South African technology company led by Justin Wessels. His work spans product design, engineering and ongoing operation.
We bring that product perspective to external work. Team composition, deliverables, timeline and support are agreed for each engagement.
Meet the founderUseful things to share up front
The problem you are solving; who will use the product; existing systems or code; required platforms and integrations; and any budget or timing constraints.
Tell us about the projectQuestions worth answering early.
What should a first brief include?
Describe the people who will use the product, the task it should help them complete and what exists today. Include essential integrations, a target date if there is one, and any budget constraints. An incomplete brief is enough to start identifying the right questions.
How do you decide what belongs in the first release?
Start with an end-to-end user journey that delivers something useful. Separate essential requirements from assumptions and later improvements. Agree how the result will be reviewed so that scope is tied to observable behaviour.
Can the work start with an existing product?
Yes. The initial scope can focus on understanding an existing application, its dependencies and the changes needed. Access, review effort and the intended outcome should be agreed before committing to a wider implementation.
What happens around launch and handover?
Release planning should cover deployment, account ownership, configuration and the information needed to maintain the product. Ongoing support and future development are defined as part of the engagement, with responsibilities agreed explicitly.