Tribe is a community platform helping organisers run memberships, events and payments in one place. As Product Lead, I shaped the strategy, UX and UI from the ground up, turning a tangle of workflows into a product organisers actually enjoy using, and members keep coming back to.

1.Discover
2.Ideate
3.Plan
4.Design
5.Test
Stakeholder interviews
Community Lead interviews
Competitor analysis
IA & Sitemap
User archetypes
Concept exploration
Roadmap planning
Sprint planning & Backlog refinement
Feature deep dives
Design system
High fidelity designs
PDRs
Prototyping
User testing
Design Iterations
QA & deployment testing
1.Discover
2.Ideate
3.Plan
4.Design
5.Test
Stakeholder interviews
Community Lead interviews
Competitor analysis
IA & Sitemap
User archetypes
Concept exploration
Roadmap planning
Sprint planning & Backlog refinement
Feature deep dives
Design system
High fidelity designs
PDRs
Prototyping
User testing
Design Iterations
QA & deployment testing

Management & Strategy
As Product Lead at Tribe, I held dual ownership of both product direction and design, leading a cross-functional team while personally delivering all UX and UI across the product.
On the product side, I ran the team day-to-day: facilitating standups, structuring our ways of working in ClickUp, managing sprint planning, and keeping stakeholders aligned.
Design & Execution
On the design side, I was the sole designer, responsible for everything from early concept and user research through to final UI, design system, and iterative improvements based on ongoing user testing with real community members.
Crucially, I built the product from the ground up. There was no existing foundation to work from, the design language, component library, processes, and product decisions were all established from scratch over the past year. This dual role meant balancing strategic thinking with hands-on execution every day, in a live startup environment where priorities shifted and real users informed every iteration.


Stakeholder interviews

Community Lead interviews

Competitor analysis

Stakeholder interviews

Community Lead interviews

Competitor analysis

IA & Sitemap

User archetypes

Roadmap planning

Sprint planning & backlog

Feature deep dives

Roadmap planning

Sprint planning & backlog

Feature deep dives




Concept Exploration
With the structure defined, the next step was exploring how it could come to life visually. Rather than jumping straight into high fidelity, concept exploration was about trying different directions, testing how the product could look and feel before committing to a single approach.
For Tribe, this meant exploring how a community platform could feel distinct from the social apps people already used every day. The goal wasn't to reinvent the wheel but to find a visual and interaction language that felt native to the type of communities Tribe was built for, engaged, interest-led, and human.
Given the pace of the startup, these explorations were focused and intentional rather than exhaustive. Each direction was evaluated quickly against what we knew about our users and the product vision, allowing decisions to be made fast without sacrificing the quality of the final output.

Design System
Once the design concept was chosen, I built the foundation from scratch , defining colour, typography, spacing, and iconography before building out a full component library. Every element was created once, documented, and reused consistently across the product.
Maintaining and evolving the system was an ongoing responsibility throughout the year. As new features were designed and the product grew, components were refined, new patterns introduced, and the system adapted to meet new challenges , ensuring Tribe stayed visually consistent no matter how fast we were moving.













High Fidelity Designs

PDR’s & Functional Specs

Prototyping
Before any feature reached the development team, it was prototyped, bringing the high fidelity designs to life to validate interactions and user flows before a line of code was written. Prototypes were built in Figma and used directly in user testing sessions with community leads, giving a realistic enough experience to surface real feedback.
This step was what turned static designs into something the team could rally around and stakeholders could actually respond to.

User testing
With a prototype ready, I tested each feature with community leads over Google Meet, observing how they navigated the journey, where they hesitated, and what didn't work as expected. Recruiting from within the community meant feedback came from real, invested users rather than generic testers.
Every session fed directly back into the design before release, iterated on until the experience was right before it ever reached the wider community.

Prototyping
Before any feature reached the development team, it was prototyped, bringing the high fidelity designs to life to validate interactions and user flows before a line of code was written. Prototypes were built in Figma and used directly in user testing sessions with community leads, giving a realistic enough experience to surface real feedback.
This step was what turned static designs into something the team could rally around and stakeholders could actually respond to.

User testing
With a prototype ready, I tested each feature with community leads over Google Meet, observing how they navigated the journey, where they hesitated, and what didn't work as expected. Recruiting from within the community meant feedback came from real, invested users rather than generic testers.
Every session fed directly back into the design before release, iterated on until the experience was right before it ever reached the wider community.
Leading Tribe as both Product Lead and sole designer in a live startup environment demanded a level of ownership that shaped how I think about product and design. Managing a team, driving the roadmap, running sprints, and delivering all the UX and UI simultaneously meant operating across every layer of the product, from high-level strategy to the finest interaction detail.
Working in a startup with no fixed process, shifting priorities, and real users from day one forced a different way of thinking. Decisions had to be made quickly, validated with the community, and iterated on without losing sight of the bigger picture. That balance of speed and rigour, knowing when to move fast and when to slow down, is something you can only learn by doing.
The result is a platform that is live, growing, and continuing to evolve. A year of building in a fast-moving, resource-constrained environment has been the most formative experience of my career so far.