People hate change
and software projects.
Here's a book
about how to fall
in love with both.
01The hook
Uncertainty shrinks the moment you can touch the work.
The AI era dials the uncertainty up on every kind of work — more moving parts, fewer fixed answers, and a constant feeling that the ground is shifting. Every software project already demanded a tolerance for that fog nobody quite has.
02The turn
For the first time, the audience can get on stage.
AI just collapsed the cost of visualising and building working software. What used to take months of slides, specs and guesswork can now be prototyped in days — real, clickable, running software the people who'll actually use it can try, react to, and reshape before a single line is locked in. That small shift quietly rewrites how decisions get made, who gets a say, and what your money actually buys.
We call it the Mearra Method. The book is the rest of that sentence.
03The shift
Less theater. More shipped.
- 01
Stop paying for software you never quite get.
Fewer nasty surprises, fewer change-request invoices, budgets that behave.
- 02
Build things people actually use.
Adoption stops being the afterthought that quietly kills projects — the people who'll live with the software help shape it, so they champion it instead of resisting it.
- 03
Get a room full of stakeholders to genuinely agree.
Turn “I'll know it when I see it” into decisions everyone understands and owns.
- 04
Make AI pay off in your business — not just your codebase.
Speed at the keyboard was never the prize; this is about what that speed finally lets your business do.
- 05
See the costs the demo hides.
Know the real number — including what happens long after launch — before you commit, so the figure you take to the board actually holds up.
- 06
Walk into your next software decision in control.
Know what to ask, what a good answer sounds like, and where the risk really lives.
- 07
Lead your people through the disruption without losing them.
Who wins, who loses, and what a decent organisation owes the people the change leaves behind.
04A peek inside
A few of the things we get into.
- 01
Touch the Software on Day One
Why working software belongs at the start of the project, not at the end of the design phase.
- 02
Software Belongs to the Business
What changes the moment the people who use it, not IT, own the thing they depend on. (And why budgets suddenly get easier to defend.)
- 03
Beyond Agile
The old rituals go, replaced by AI-era versions that cut misunderstandings and ship faster.
- 04
A Process Anyone Can Step Into
Building software shouldn't require a translator. How to make the method accessible to everyone in the room.
“We'd rather make change something people choose than something they survive.”
The Mearra Method
05The authors
A bubbly business designer and a grumpy old CEO walk into a sales meeting.
Maija Helminen
Educational scientist turned business designer. Believes progress should be accessible to everyone, and has never met a piece of gatekeeping she didn't want to call out.
Vesa Palmu
Computer scientist and CEO with ~30 years in software. Has watched every hype cycle come and go, and stays productively sceptical about this one too.
Both work at Mearra, where the method was built — and tested on real projects, with real budgets and real consequences.
06Who it's for
Read it if…
…change feels impossibly hard, and you wonder why, in 2026, there still isn't a better way.
…"agile" stopped meaning anything useful in your organisation.
…you want your software project to actually land — something people adopt, not just something you can demo.
Half for the people deciding what to build. Half for the people building and securing it.
07Final call
The magic show is ending.
Be in the room when it does.
Leave your email. We'll send the first chapter and tell you the moment the book ships. No noise. No newsletters about newsletters.
Curious about the method in practice? → mearra.com