Insight
Insights
What if governance isn’t actually your problem?
Published on
29 May 2026Category
Insight
Five shifts for product teams working inside complex organisations – and why the conditions you have are more workable than they appear.
There’s a version of the product role that gets a lot of airtime. It’s greenfield. The team is empowered, the technology is modern, decisions happen quickly, and there’s a clear roadmap to build from.
Most people working in large organisations will recognise how rarely that version materialises.
What they find instead is messier and more familiar: legacy systems nobody wants to touch, governance processes that move slowly, Risk and Compliance functions with a default disposition toward caution, budgets already committed before you arrived, and release cycles locked months in advance. Roles that exist on the org chart but not in the room.
The gap between expectation and reality is real, and it’s widely shared – even among experienced practitioners who’ve navigated complex environments before.
At Signal Not Noise in Adelaide this month – a conference for lean, agile and systems thinkers who appreciate a practical idea over a polished one – Escient Principal Consultant, Olga Belokourova, offered a way of thinking about that gap that’s more productive than frustration, and more honest than pretending it doesn’t exist. Drawing on 25 years of delivery experience across startups, SaaS providers, a major bank, and consulting, her session shared five practical shifts for building good work inside constrained systems.
The premise underneath all five: large organisations aren’t broken. They’re constrained. And constraint, approached well, is material to work with. The job isn’t to build the perfect product inside perfect conditions. The job is to expand what’s possible inside imperfect systems.
Risk, Compliance, Legal and Cyber functions are not there to stop delivery. They exist to reduce harm, and that’s a legitimate purpose worth understanding rather than resisting.
The shift is moving from “can we get this approved?” to “what would make this safe enough to build and launch?” A small change in wording that materially changes the relationship.
When Governance only sees finished work, its options are limited. Approve or stop. The work is already formed, the direction already set, and any concern raised means undoing something rather than shaping something. Bring them in earlier, when work is still forming, and they become stakeholders in the outcome rather than judges of the result. Design partners rather than gatekeepers.
In practice this means sharing early thinking rather than finished artefacts, co-designing experiments rather than presenting them for sign-off, and engaging before approval is needed rather than at the point it becomes urgent.
The assumption that good product work requires better conditions – more budget, more time, more modern technology – is understandable, and rarely the reality.
Constraints force sharper thinking and better prioritisation. Fixed release trains are genuinely limiting in some respects, but they’re also a forcing function for prioritisation, which is where real product thinking lives. A constrained budget pushes teams toward reversible bets over irreversible ones, often producing better discipline than an open budget would. The constraint and the useful behaviour it creates aren’t separate things.
Three questions help surface what’s actually workable in any constrained environment: What is truly fixed? What is flexible? And the most productive of the three – what are we treating as fixed that is actually negotiable? That third category tends to hold more room than people expect.
Product teams under pressure sometimes move quietly. Keep the experiment small, avoid the risk conversation, get results, and present something proven rather than something proposed. It’s a recognisable pattern, and it occasionally creates short-term speed.
The longer-term cost is trust. Working around governance might feel efficient in the moment, but it damages the working relationships that matter most over time. When Risk discovers it was bypassed – and in most organisations, it does – the next engagement is harder, and the gate becomes heavier.
Strong product leaders design experiments with governance functions, not around them. That means agreeing on four things before starting: the hypothesis being tested, the impact boundary of the experiment, a rollback plan if things don’t go as expected, and the risk signals both sides will monitor. Governance teams, presented with that frame, tend to be far more comfortable than they’re given credit for. Controlled uncertainty is something they can work with. Invisible uncertainty is something they’re structurally required to stop.
In large organisations, the fully-resourced, perfectly-aligned product team is more aspiration than reality. Most teams are doing good work with what they have – which is usually capable people navigating conditions that are rarely ideal.
The goal isn’t to wait for ideal conditions but to create stability, clarity and momentum inside imperfect environments.
Leading well in those conditions starts with honesty about them. Performing around constraints – acting as though the team is more resourced or more aligned than it is – doesn’t make them disappear. It just means they surface at the worst possible moment. Naming constraints openly creates the conditions for working around them. Designing around actual strengths, reducing cognitive load through clear decisions and ownership, and building regular clarity rituals gives stretched teams the orientation they need to keep moving.
Language shapes culture and thinking in ways that accumulate quietly over time.
Many organisations become trapped in “why can’t we?”- a framing that positions constraint as permanent and externally imposed. When the default response to complexity is a list of blockers, that becomes the team’s relationship with its own work.
High-performing product teams shift toward different questions: What can we move? What is the smallest safe step? What decision can we make today? These questions build the habit of looking for agency within constraint rather than waiting for it to be removed.
Practised consistently, that habit compounds. Progress often starts with reframing the conversation, and teams that develop this habit tend to find they can move more, deliver more, and advocate for more over time.
The most effective product managers are rarely the ones with the cleanest roadmaps, the newest technology, or the most ideal conditions.
They are the ones who focus on what is possible – and then expand it. Good product work doesn’t wait for clean conditions. It finds a way inside the ones that exist, and then makes a little more possible each time.
Olga Belokourova is a Principal Consultant at Escient, specialising in product delivery and digital transformation across financial services, health, utilities, and the community sector.
