Because it shouldn't be hard
Practical support for projects when things feel stretched, unclear or complicated. Putting the pieces together, without fuss.
Because it shouldn't be hard
Practical support for projects when things feel stretched, unclear or complicated. Putting the pieces together, without fuss.
We work across project set-up, delivery and recovery — helping teams bring clarity, momentum and informed decision-making where it matters most.
Helping teams start well — or take a step back and reset when things feel unclear.
This might include defining scope, roles and programme, or simply creating space to think clearly before moving forwardd.
Hands‑on support where needed — bringing experience, structure, and calm to keep projects moving..
We work alongside teams to reduce friction and support delivery.
Experienced, pragmatic input during periods of change, pressure, or uncertainty.
Sometimes what’s needed is simply another pair of steady hands.
Oshigoto was set up to provide calm, practical support where projects don’t quite fit neatly into traditional roles or structures.
Over time, projects tend to accumulate complexity — not because anyone is doing a bad job, but because scope expands, responsibilities blur, and pressure increases. Oshigoto exists to step into those moments and bring clarity, structure, and judgement.
We work across project set‑up, delivery and reset — supporting teams when something needs shaping, steadying, or re‑aligning.
Because it shouldn’t be hard
Oshigoto is deliberately small and senior.
The work is hands‑on, embedded, and proportionate to what’s needed — not formulaic and not overly process‑led.
Engagements may be short and strategic, or longer and more embedded, depending on the challenge. The common thread is focused support that helps teams think clearly and move forward with confidence
Most projects begin with a conversation.
Sometimes that leads to a short piece of advisory input.
Sometimes it develops into more sustained project or delivery support.
Either way, the aim is the same:
Oshigoto brings together experience gained across architectural practice, client-side organisations and contractor environments.
That breadth of experience supports projects from early strategy and briefing through to technical coordination, delivery and project recovery.
The perspective behind Oshigoto has been shaped by more than three decades working across complex programmes where decisions need to be practical, proportionate and capable of standing up to real-world delivery.
Engagements remain deliberately senior, hands-on and proportionate to the challenge, without unnecessary layers or dilution of responsibility. C
Honest project health checks. Calm, senior diagnosis. Practical fixes.
Coordinated, compliant, contractor‑ready information — so redesign doesn’t happen on site.
We work best with:
This way of working isn’t theoretical.
It’s been tested on complex, high‑risk projects at serious scale.
Large workplaces. Phased refurbishments. Live buildings. Long programmes. Multiple stakeholders.
Our experience includes projects for people like:
Shell
Bloomberg
MAN Group
Hearst
Bayer
Roles varied. Responsibilities shifted. What didn’t change was the need for clear thinking, strong coordination, and decisions that held up on site.
Feasibility, test fits, early diagnostics, and risk‑led thinking that prevents false starts.
Unpicking complexity. Clarifying roles. Re‑establishing momentum without adding noise.
Plug‑in architectural leadership, design management and coordination—focused where it matters.
From early strategy through technical design and delivery, we understand how decisions made on paper play out on site. That perspective shapes everything we do.
Over the last few weeks, I've seen plenty of conversations about Artificial Intelligence. Some are excited. Some are terrified. Most seem convinced it's either going to save civilisation or destroy it. The first was a clip from Ben Affleck arguing that AI is likely to become a powerful tool, but that creativity, judgement and experience remain fundamentally human skills.
Personally, I'm somewhere in the middle.
Perhaps that comes from spending more than twenty years watching technology transform how we design, coordinate and deliver projects. When I started my career, drawing boards were still part of the landscape. CAD then became the future. CAD became BIM. BIM moved into cloud collaboration. Today we're talking about AI-assisted workflows. Every generation seems convinced that the latest technology will change everything. Sometimes it does.
What I've noticed, however, is that the technologies creating the biggest impact are rarely the ones that replace people. They're usually the ones that remove friction.
The repetitive tasks. The administrative burden. The delays in finding information. The things that get in the way of good work. That's where I think AI has enormous potential.
As designers, project managers and construction professionals, we spend a surprising amount of time searching for information, checking information, coordinating information and communicating information. AI can help with a lot of that.
What it can't do, at least not yet, is understand context in the way experienced people do.
My course leader was originally a Fine Artist from Glasgow School of Art who found his way into design through model-making for Ford, working on the now iconic Ford Anglia.
Colin had us sketching constantly. Not just in life drawing classes, but throughout design development, project critiques and problem-solving. A sketchbook wasn't optional. It was part of how we learned to think. His philosophy was simple:
"You have to get past the point of asking 'How do I draw that?' and get to the point where you ask, 'How do I want that to work?'"
At the time, he was talking about drawing and design. Looking back, I think he was really talking about thinking.
Too often we end up designing for the software, rather than asking the software to help us design what we actually want to build. Every architect, designer, engineer and contractor has seen that happen at some point.
The software becomes the process. The model becomes the objective. The tool starts influencing the solution. Colin's point was the opposite.
Focus on the outcome first. Then use the tools available to help get there. That's why the current AI debate doesn't worry me as much as some people.
AI is already becoming very good at answering:
"How do I draw that?" What experienced people still excel at asking is: "What am I trying to achieve?" Those are very different questions. One is about producing an answer. The other is about understanding the problem. It doesn't attend stakeholder meetings.
It doesn't walk around a building and sense when something doesn't feel right. It doesn't understand the experience of a space, how you enter it, how it feels or how its proportions affect the people using it. It doesn't recognise that a technically correct solution may still be the wrong solution for a client or the design. It doesn't take responsibility when a difficult decision needs to be made. As a mate says “AI has no PI”
Most importantly, it doesn't carry the experience that comes from years of solving real-world problems.
The projects I've always enjoyed most are the difficult ones. The projects where expectations don't align. The programme is under pressure. The design and construction teams are pulling in different directions. The project is, to use a technical term, wobbling. The value rarely comes from producing another drawing or another spreadsheet.
The value comes from understanding the situation, connecting the dots, bringing people together and helping the team find a way forward. That's fundamentally a human skill. I suspect AI will become another powerful tool in our toolbox.
Just as CAD didn't eliminate designers. And BIM didn't eliminate Design Managers. AI won't eliminate the need for judgement, leadership, experience and accountability.
The challenge isn't whether AI can produce an answer. The challenge is knowing whether the answer is any good. That's where experienced people still matter. Perhaps the most important question isn't:
"What can AI do?" But: "What should we ask it to do?"
Used well, AI can help remove friction, accelerate thinking and improve productivity.
Used badly, it risks creating more noise, more dependency and more confidence in answers that haven't been properly challenged. Like any tool, its value depends on how thoughtfully we use it. The software may hold the shovel. We still need to know where to dig.
Perhaps my Gen X upbringing also influences my thinking.
After all, we've spent decades being warned about AI by WarGames, Terminator, RoboCop and The Matrix. AI is an incredibly powerful tool. The challenge is making sure we don't let the tool replace the thinking.
I'll probably start worrying a little more when AI turns up in a leather jacket, riding a Harley-Davidson and speaking with a thick Austrian accent.
Until then, I suspect it's more likely to be another tool than the end of civilisatio.
Jack Pringle once asked Nick Grimshaw how Grimshaw's projects consistently remained contemporary and creative.
The answer was surprisingly straightforward.
“Peer review. Everything gets reviewed by everyone. Even mine.”
That response highlights something often misunderstood about good design.
Good design is not simply originality, nor is it the product of the strongest personality in the room.
The most effective projects emerge through a shared process. Ideas are tested, challenged, refined and improved before they ever reach a client.
The role of leadership shifts in that environment.
It is no longer about holding the “thinking stick”. It becomes about recognising, guiding and elevating the best ideas, regardless of where they originate.
Design is not just origination.
It is direction.
And the ability to shape outcomes through others is what once defined the role of a Design Director.
A lot of complexity creeps in when the wrong people start driving decisions.
Not because they lack intelligence —
but because they don’t own the consequences.
Projects drift when influence outweighs accountability,
when career priorities quietly override project priorities,
and when decision‑making sits with the wrong skill sets.
Clarity returns once decisions are owned
and the project itself is allowed to come first.
Revit is a powerful authoring tool. BIM is a way of deciding how information is created, shared, and relied upon. Confusing the two often leads to projects carrying more risk than anyone intended.
Authoring in Revit does not automatically mean better coordination, nor does it, by itself, justify higher fees. The more important questions are about scope, responsibility, and what information is actually required to make sound decisions at each stage.
There is often an enthusiasm to make the model work too hard — to model every fixing, junction, or component. In practice, understanding boundaries and strengths is far more valuable. Much of what sits beyond a 1:20 level adds complexity rather than clarity.
Used well, Revit’s real strengths sit elsewhere: scheduling, specification links, coordination checks, and the ability to generate consistent visuals and walkthroughs from the same source of information. When this is understood early, projects avoid duplication, re‑work, and the familiar pattern of parallel models being rebuilt downstream.
When those questions aren’t addressed early, BIM doesn’t become more helpful — it simply becomes louder.