For twenty years I’ve watched teams struggle with the “how” of product work. The Build Loop is my answer.

What Skysoclear is

Skysoclear is a small product practice, run by me. I help teams decide what’s actually worth building, and build enough of it themselves to know.

The work is two days, in person, with your team. We frame the decision you’re stuck on, build a working prototype in the room, put it in front of real users, and make the call (ship, iterate or kill) with evidence your sponsor can defend. You leave with a 90-day plan and the templates to run the next loop yourselves. How we help

It’s for product, digital and innovation leaders with a build decision that’s too expensive to get wrong, usually in insurance, wealth, financial or professional services. Teams of two to eight, in the UK. It works best when the person who can make the call is in the room.

Who I am

I’m Ross Chapman. I’ve been Head of UX, Head of Design and fractional product strategist for Fortune 500 companies and professional institutions, across insurance, wealth management, fintech, SaaS and membership bodies.

I’ve run around 200 design sprints over six years. Enough of them to see the same pattern repeat: the teams that got somewhere weren’t the ones with the best facilitator or the cleverest framework. They were the ones where real knowledge of the sector met a way of working that reliably produced a decision. Their expertise, my method. Neither is enough on its own.

The Build Loop is what I built out of that. It works in practice, not just in theory. I use the tools I teach on real client work every day.

Why I’m building this

Design thinking and the design sprint were built for a world where building was expensive. When it took months and a team of engineers to find out whether an idea worked, it made sense to spend weeks de-risking it on paper first. That world has gone. Building is now cheap, fast and available to almost anyone, and the methods that were designed around the old constraint are solving a problem most teams no longer have.

The constraint moved. It isn’t “can we build it” any more. It’s “are we building the right thing, and how would we know.”

The studio model has the same problem, and it had it before AI. A studio takes the brief, makes the product and hands it back. But it’s hard to take ownership of something you didn’t build. The team inherits a thing they can’t explain, can’t defend and didn’t choose, and the capability walks out of the door with the agency.

So the gap I’m filling is narrow and specific: helping teams decide what’s actually worth building, and building enough of it themselves to know. That’s what the Build Loop is: my framework for how businesses solve big problems in a world that keeps getting more complex.

What it’s like in the room

There’s a point on day one where I hand out thick markers and blank sheets of paper and ask everyone to sketch a solution. Everyone, whatever part of the org chart they sit in. The markers are deliberate: at that thickness a director’s sketch and a junior developer’s sketch look equally rough. Nobody’s idea wins on polish.

No group brainstorm, no building on each other’s suggestions until they average out into something safe. Individual work first, then we look at all of it together. The answer can come from anyone, and it often comes from someone who wouldn’t have spoken up in a normal workshop.

I time every activity, visibly. Work expands to fill whatever time it’s given, and longer meetings don’t produce better decisions. Most of what I’m doing across the two days is managing the energy in the room so the team gets the most out of the time they’ve committed.

Where I stand

01

Consensus produces weaker bets.

The more people who have to agree, the safer the idea gets. Everyone should contribute to the solution. One person decides.

02

A recommendation isn’t a decision.

Recommendations get discussed at the next meeting. Decisions get built.

03

Evidence beats opinion.

What people actually do tells you more than what the most senior person in the room thinks. So the prototype goes in front of real users, and finding them is something you commit to before we start.

04

Speed only counts in the right direction.

You can go very fast doing the wrong thing. Make a bet, build the smallest version of it, put it in front of the people it affects, and let what they do tell you what’s next.

What I’ve got wrong

The mistake I’ve made most often is listening to the wrong people.

In user testing that means promoters and your best customers: the ones who already like you, who’ll be generous about a rough prototype, and who tell you what you were hoping to hear. In the room it means a senior stakeholder who isn’t close enough to the problem to know what they don’t know, and whose confidence fills the gap.

Both are easy to miss, because in both cases the feedback sounds like validation. So I now design against it. Who gets tested, who gets asked, and who is allowed to be certain in the room are all decisions I make deliberately rather than by default.

Who this isn’t for

I’d rather say this plainly than find out on day two.

It won’t work if you can’t commit the time, the money and the space. Two days means two days: the right people in the room, not dipping in between calls.

It won’t work if the team isn’t willing to work in an unfamiliar way. The format asks people to do things they haven’t done before, and it falls apart if the room is waiting for it to be over.

And it won’t work if the people involved have checked out. I can manage the energy in a room. I can’t manufacture it.

I’m also not an outsourced delivery outfit. I won’t just build an app or a website, and I don’t do branding. If what you need is a supplier to take a defined brief away and return it finished, I’m the wrong call, and I’ll say so on the first conversation rather than three weeks in.

I’m not looking for an easy yes, and I’m not looking to land and expand. I go in, help you set a direction, start you on the path, and stay long enough that you can keep going without me.

If this sounds like how you’d want to work, talk it through.

Talk it through →

© 2026 Skysoclear Ltd. Registered address: Skysoclear, 20 Wenlock Road, London, England, N1 7GU. Privacy · Terms · Contact

Existing client? Login