Rebrand as Product Approach
"With the rebrand at Miro, it was very much rebrand as a product approach. It was very much a product development process with sprint teams and agile, coming back, and you had owners for different parts of things and all reporting back and it really required everybody in some way to be involved." - Barbra Gago
What It Is
The Rebrand as Product Approach treats a company rebrand not as a marketing project but as a product development initiative. This means applying product methodology—sprints, agile iterations, stakeholder owners, customer feedback loops, and cross-functional collaboration—to the complex task of changing a company's identity.
Barbra Gago developed this approach while leading the rebrand of RealtimeBoard to Miro. The stakes were high: they had millions of users, a hundred employees, and completed the entire rebrand—from naming through a full brand system to a three-dimensional booth at South by Southwest—in about four months.
How It Works
The framework applies product development principles to rebranding:
Sprint Structure
- Break the rebrand into discrete phases with clear milestones
- Run iterative cycles with regular check-ins
- Maintain velocity while allowing for feedback
Ownership Model
- Assign owners for different brand elements (visual, verbal, product integration)
- Create clear accountability without bottlenecking on marketing
- Enable parallel workstreams
Customer Involvement
- Run case studies with existing users throughout the process
- Get feedback on logos, designs, and brand concepts
- Balance customer input with execution speed
Cross-Functional Integration
- Legal for contracts and trademark issues
- Product for in-app changes
- Sales for deck and collateral updates
- Engineering for URL and technical changes
How to Apply It
Phase 1: Naming (if applicable)
- Kick off naming exploration with clear criteria
- Involve key stakeholders in naming workshops
- Check trademark availability early
- Get customer feedback on top candidates
Phase 2: Visual Identity
- Assign sprint teams to visual system development
- Iterate on logos, colors, typography
- Preserve essence of original brand where valuable
- Get early customer feedback to validate direction
Phase 3: Integration
- Map all touchpoints that need updating
- Assign owners for each integration area
- Run parallel workstreams for website, product, collateral
- Coordinate dependencies across teams
Phase 4: Launch
- Coordinate timing across all touchpoints
- Have contingency plans for last-minute issues
- Communicate changes to customers proactively
- Celebrate with the team to build internal buy-in
When to Use It
Use this approach when:
- The rebrand involves significant changes (name, visual identity, positioning)
- Multiple teams and functions need to be involved
- You need to move quickly without sacrificing quality
- Maintaining stakeholder alignment is critical
- Customer relationships are valuable and need preservation
Consider simpler approaches when:
- Only minor brand refreshes are needed
- The company is very small
- Changes are purely cosmetic
Source
- Guest: Barbra Gago
- Episode: "Category creation and brand building | Barbra Gago (Pando, Miro, Greenhouse, Culture Amp)"
- Key Discussion: (34:46-37:35) - Full discussion of the product approach to rebranding and lessons learned
- YouTube: Watch on YouTube
Related Frameworks
- Product Development Lifecycle (DSBL) - The product methodology that inspires this approach
- Three Questions to End a Meeting - Useful for rebrand coordination meetings