About Broaden
Built for the space between the idea and the system it requires.
Broaden Labs is a software product studio for organizations building something that matters enough to get the details right.
We combine product thinking, design, and engineering because the most consequential decisions rarely belong to only one discipline.
Software changes what an organization is capable of doing.
That's why we don't treat development as order fulfillment.
The job is not to translate a requirements document into screens.
The job is to understand what the organization is trying to make possible—and then design the product, architecture, and implementation capable of carrying that ambition.
Why "Broaden"?
To broaden is to increase the range of what is possible.
A better workflow broadens what a team can accomplish.
A better platform broadens what a business can offer.
A better architecture broadens how far a product can evolve.
Technology matters when it creates room to move.
That's the idea behind the name.
What we hold to
Think in systems.
A screen is connected to a workflow. A workflow is connected to data. Data is connected to architecture. Architecture is connected to the business.
We design with the whole system in view.
Make complexity earn its place.
Sophistication is useful. Complication is expensive.
We know the difference.
Care after it works.
"Functional" is the beginning.
The spacing. The empty state. The error message. The loading behavior. The keyboard path. The response time.
The final ten percent determines how the product feels.
Explain the decisions.
Good partnerships don't depend on mystery.
We communicate the reasoning behind recommendations so teams can make better decisions long after an engagement ends.
The team
Demo profiles — these people are fictional
Broaden is a new studio and its team is not yet public. The profiles below are fixture records that exist so the component could be built and tested. Portraits are generated compositions, not photographs of anyone.
-
Adrian Vale
Founder / Product Engineering
Adrian works at the point where a product decision becomes an architectural one. He started Broaden after a decade of watching good ideas get diluted in the handoff between the people who imagined them and the people who had to build them.
- Product architecture
- Domain modelling
- Technical strategy
-
Maya Chen
Design Director
Maya designs the states nobody asks for — the empty one, the failed one, the one with four hundred rows. She is unusually interested in data density, and unusually stubborn about the moment an interface stops explaining itself.
- Interaction design
- Design systems
- Information architecture
-
Elias Morgan
Principal Engineer
Elias builds systems for the day they are under load and something has already gone wrong. Most of his work concerns distributed state, and most of his opinions concern what should happen when a connection drops.
- Distributed systems
- Real-time architecture
- Performance
-
Sofia Reyes
Product Strategy
Sofia’s first question is rarely about the product. It is usually about the business model underneath it, because that is where most feature disagreements actually originate. She turns ambiguity into decisions teams can act on.
- Product discovery
- Business modelling
- Roadmap definition