Ugo Mbelu
Ugo Mbelu is the founder of Olumba, a project management platform built for architecture and engineering firms during the design phase. He's also VP of Operations at Icon & Ikon, Inc., an architectural design-build firm, where he manages project delivery from schematic design through construction.
Over 10+ years in project management, expediting, and construction management, Ugo saw the same problems repeat across every project: version confusion on drawing sets, decisions lost in email threads, consultants working from outdated files, clients surprised at presentations because nobody kept them in the loop between milestones.
He built Olumba to solve those problems for small and mid-size A&E firms — the ones too small for Procore but too serious for spreadsheets and shared drives.
He writes about the project management, document control, and team coordination problems that design teams deal with every day — from the perspective of someone who's dealt with them firsthand.
All posts
Drawing Numbering for Multi-Discipline Sets
A drawing numbering system needs to survive a multi-discipline set with hundreds of sheets — and still make sense to someone in the field. Here's what that looks like.
Client Access Boundaries on A&E Projects
Giving clients access to your project is smart. Giving them access to everything is a mistake. Here's how to think about the right level of client visibility.
Why Email Fails on Design Projects
Email was never built for project coordination. But that's how most design teams use it. Here's what the real cost is — and what to do instead.
Why Architecture Firms Struggle with PM
Architecture firms don't struggle with PM because architects are bad managers. The problem is structural — and it starts in architecture school.
Managing Addenda and Bulletins on Projects
Addenda and bulletins are where document control goes wrong on construction projects. Here's how to manage them so the field always has the right information.
Task Systems Architecture Teams Will Use
The best task management system is the one your team actually uses. Here's how to design one that sticks — without overcomplicating it.
Client Portals for Architecture Firms
Most architects share information with clients via email attachments and shared drive links. There's a better way — and it doesn't require enterprise software to get there.
The Real Cost of Poor Document Control
Most architecture firms don't track the cost of document control failures. They should. The rework, delays, and disputes are far more expensive than the fix.
Organizing Project Documents in Architecture
There's no one right folder structure for architecture projects — but there are plenty of wrong ones. Here's a practical approach to document organization that holds up over time.
The PM Stack for Small Architecture Firms
Most small architecture firms are either drowning in too many tools or getting by on spreadsheets and shared drives. Here's what a practical PM stack actually looks like.
Client Communication by Design Phase
Most architects know what to deliver to clients. Fewer have a system for it. Here's exactly what client communication should look like from SD through CDs.
Stop Reply-All Chaos on Architecture Projects
Reply-all email chains on design projects are a symptom, not the problem. Here's what's actually causing them — and a practical approach to reducing them for good.
Design Phase Project Management for A&E Firms
The design phase is where projects get made or broken. Here's a practical framework for managing it — from schematic design through CDs — without losing the thread.
How to Track Design Decisions on A&E Projects
Design decisions made in week two can haunt you in month eight. Here's a practical system for capturing decisions in a way your whole team can actually use.
Drawing Version Control for Architecture Firms
Working off the wrong drawing version is the most expensive mistake in design. Here's how to build a version control system that actually holds up under project pressure.