Start with a useful scope
Build the first version around a clear user task. Add features when feedback shows they are needed.
Oo-ta-boo/oo-ta-boo/
The name is made up.
The work is not.
Ootaboo Pty Ltd. ABN 50 606 038 313. Registered in Australia in May 2015. Australian software product studio.
A few chapters from the workbench.
XrostersRostering & pay rules
FacenexFace + PIN payments
64dimesEcommerce
StratzTrading execution · live
Different products. Lessons that carry forward.
Eleven years of building software products.
Ootaboo has built software since May 2015, including rostering systems, biometric payments and ecommerce. Some products worked technically but failed commercially. Others were retired. The case studies explain what we built and what we learned.
Stratz is our current live product. It applies lessons from earlier builds to trading execution: check each account before sending an order, manage protective orders and reconcile records with the exchange.
Read the Stratz case studyWhat earlier builds taught us
- Technical success does not guarantee commercial success.
- Users did not value some of the features we built.
- Early versions should have been simpler.
- Operational complexity taught us to design for production behaviour.
- Systems needed stronger controls before handling real money or real data.
Engineering
philosophy.
Experience changes how you build.Design for production
A working demo is a start. Before launch, the system also needs to handle failed requests, unexpected inputs and recovery.
Make system behaviour visible
Logs and operational records let us trace what happened when something fails and check whether a change fixed it.
See the product evidence.
Read the case studies for each product's scope, architecture and current status.