A job you give to Aurora
Improve a product
Aurora understands, researches, decides, does, reviews and measures.
More specialized work. Less structure to get it done.
What always had to be built for this
- People
- a product lead, developers
- Specialists
- user research, design, data
- Vendors
- studio, testing
- Software
- analytics, design, development
- Management
- a product lead
- Coordination
- cycles, reviews
Now it is a job you give to Aurora
How Aurora would do it, stage by stage.
1/7
Understands
Before doing anything, it understands your company and what you want.
ExampleImprove a productIt asks youWhich product, which customers use it, what they complain about, and what you want improved.
2/7
Researches
It looks for evidence. What it does not know stays marked as unknown.
ExampleImprove a productIt opensReal usage, complaints, reviews, what similar products do, your support data.
Stays unknownWhat customers do not say, until asked.
3/7
Decides
It decides what work is needed. You do not have to know in advance.
ExampleImprove a productIt proposesImprove the two things that generate the most complaints and measure whether they drop.
It discardsRebuild the whole product: there is no evidence for that.
4/7
Does
It does the work. It executes only what you authorize.
ExampleImprove a productIt asks you to authorizeRead your usage and support data. Yes. Publish changes to your customers: only if you authorize it.
It deliversTwo designed improvements, a customer test, and how to measure the effect.
5/7
Reviews
Done is not taken as good. It is checked before delivery.
ExampleImprove a productOne caseOne improvement solved a complaint but created another. Redesigned before proposing it.
6/7
Measures
Doing something is not achieving it. It measures what happened.
ExampleImprove a productWhat it didThe improvements are delivered and tested.
What happenedComplaints and usage, one month later, with your data. Before that, not measured.
What it did ≠ What happened
7/7
Learns
What worked stays for the next job. New evidence corrects it.
ExampleImprove a productWhat staysWhat lowered complaints stays. What did not is recorded so it is not repeated.
Start with a diagnosis.
Up to two weeks, on your data. It ends in “this is possible, this is not, and this is what it would take”. If it is not useful, you stop there.
Price agreed before starting. No subscription, no standing team.