We've been building together since 2011. What started as a partnership grew into IDESIGN Media: a digital studio where strategy and design worked together from day one. Brands, websites, bespoke web applications across Aotearoa. Good work. Happy clients. But over the last few years, the projects kept getting bigger. More bespoke. Higher stakes. And we kept noticing the same thing: the industry's approach to delivering complex digital projects was broken. Today, we become RIVER.
How We Got Here
We built IDESIGN on form and function. But the work evolved. Over more than a hundred projects, clients started coming to us with harder problems. Not "we need a website" but "we need a platform that handles X, integrates with Y, and has to work for 500 people on day one." Custom web applications. Enterprise portals. Systems where the brief couldn't be pulled from a template because the problem had never been solved before.
That shift changed everything. When you're building a five-page marketing site, the process is forgiving. When you're building a bespoke enterprise system with real users, real integrations, and real consequences if it doesn't work, the process is everything.
And the processes we saw across the industry weren't cutting it.
The Problem With How Projects Get Built
16%
of enterprise IT projects completed successfully in 2018
Source: Standish Group CHAOS Report, 2018
In 2018, only 16% of enterprise IT projects completed on time, on budget, and with full objectives met. Over 31% failed outright. Globally, organisations were wasting roughly 12% of their entire project investment due to poor delivery.
We'd seen it ourselves. Not in our own projects, but in the wreckage clients brought to us after working with others. Builds that ran for 18 months without showing the client working software. Agile teams sprinting in circles with no clear destination. Projects where the people who'd actually use the system hadn't been consulted since the kickoff meeting.
The industry had split into two camps, and both were losing.
Pure waterfall gave you a vision and a plan, but by the time you delivered, the world had moved on. Requirements were stale. Users had changed. You'd built exactly what was specified and precisely what nobody needed anymore. Lidl spent seven years and over €500 million on an SAP implementation that was ultimately scrapped. Hertz sued Accenture for $32 million over a website redesign that never launched.
Pure agile gave you speed and feedback, but often no destination. Teams shipped increments that felt productive but never added up to a product with purpose. "We'll figure it out as we go" became an excuse for never defining where "there" was. The agile industrial complex had turned a good philosophy into a certification industry, and the outcomes weren't changing.
We didn't buy either extreme. We believed in both.
What We Built Our Practice Around
- Start with people and outcomes. Every failed project we'd seen had one thing in common: the people who'd use the product were the last to be consulted. We put them first.
- Have a vision. Know where you're going. The best of waterfall is clarity of destination. Every project needs a north star, a clear picture of what success looks like, agreed before a single line of code is written.
- Build dynamically. Get feedback constantly. The best of agile is the feedback loop. Deliver in stages. Put work in front of real users. Listen. Adjust. Repeat.
- Manage risk in real time. Don't save the risk conversation for a quarterly steering committee. Surface it weekly. Talk about it with the client, not about the client.
- Balance function and form. Technical capability without design thinking builds tools people tolerate. Design without engineering depth builds beautiful things that break. You need both, from day one.
The Delivery Philosophy
We call it Vision, Roadmap, Execution. Know the destination. Map the route. Build in stages with constant feedback. As bespoke projects became our focus, this philosophy became our practice, and it's what started building a delivery record we're proud of. Every project delivered. Every one.
We begin every engagement centred on outcomes. What does success look like for your organisation, not in technical terms, but in business terms? Who are the people this will affect? What does their day look like now, and what should it look like after?
Then we set direction. A clear vision, a defined scope, a shared understanding of what we're building and why. The strategic discipline that keeps a project from drifting. Knowing the destination before you start moving.
Then we build in stages, with the client in the room. Not a quarterly review. Genuine involvement. Seeing working software, giving feedback, shaping the product as it takes form. The dynamic discipline that keeps a project grounded in reality.
And throughout, we manage risk together. If something changes (budget, scope, user feedback, market conditions), we talk about it immediately and adjust course together. No surprises.
Too many projects fall over because the methodology matters more than the outcome. We took the best of both and threw away the dogma.
Isaac Rolfe
Managing Director
Function and Form
This is what makes RIVER different from a pure dev shop or a pure design agency. We're both, and that's deliberate.
Isaac leads strategy and technical architecture. Rainui leads design and user experience. And the team we've built around that leadership - developers, designers, project managers - carries the same standard into every engagement. Everyone in the room understands both disciplines, because that's how we hire and how we work.
Too many enterprise projects treat design as a skin applied at the end. We've never worked that way. Design is in the room from discovery through to delivery. It shapes the architecture as much as the architecture shapes the interface. The result is products that work well and feel right, because both disciplines informed every decision.
When you're building software that someone will spend eight hours a day using, this matters. It's the difference between adoption and resistance, between a system that transforms a workflow and one that gets worked around.
Enterprise systems have the lowest bar for design and the highest stakes. If we don't get the experience right, no amount of engineering saves it.
Rainui Teihotua
Chief Creative Officer
Why RIVER
We chose the name deliberately.
A river has direction. It knows where it's going. But it's dynamic. It adapts to the terrain, finds the path of least resistance, carves new channels when it needs to. Powerful but not rigid. Purposeful but not brittle. That's how we build.
There's a deeper layer too. In te ao Māori, water (wai) carries significance beyond the physical. Rivers connect communities. They sustain life. They flow in one direction but nourish everything they touch. As a Māori and Pacific-owned company built in Aotearoa, this resonance matters to us. RIVER isn't just a metaphor for how we work. It's a reflection of who we are and how we see our role, connecting technology with people, flowing toward outcomes that sustain.
We worked through the rebrand with Ira, a Māori design studio that specialises in culturally grounded brand and strategy work. Johnson McKay and the Ira team helped us think through what RIVER actually meant, not just as a name but as a strategic direction rooted in who we are. That clarity shaped everything that came after.
This is our first post as RIVER. There will be plenty more: insights on delivery, design, technology, and the lessons we learn along the way. But this felt like the right place to start. Why we exist, what we believe, and how we intend to build.
We are RIVER. Let's go!
This is the second chapter. Read Where It Started for the origin, or skip ahead to The AI Pivot for the moment everything changed.