Aligning Consensys Around a Unified Blockchain Developer Experience
Consensys Developer
The Challenge
Despite strong brand recognition for individual products like MetaMask, Infura, and Truffle, most developers didn’t realize they were all built by the same company—Consensys. As a result, developers’ journeys into Web3—and through Consensys tools—were fragmented. Product adoption, activation, and engagement happened in silos, without a cohesive experience.
To solve this, I partnered with researcher Tyreek Houston to better understand how developers move from initial interest in Web3 to launching successful decentralized applications—and how Consensys products could better support them along the way.
Discovery & Alignment
I began by interviewing nine internal stakeholders across product, design, sales, and marketing to understand:
- Their perspective on the current developer journey
- Pain points and opportunities they observed
- What success would look like from this work
I also met with product leads to learn how each tool fits into the developer lifecycle and collected supporting documentation—product onboarding flows, marketing assets, sales decks, and internal research.
Mapping the Current Developer Journey
After synthesizing our interviews and documentation, I created a visual map of the end-to-end developer journey—from first exposure to Web3 through to launching a live dApp. The map revealed key patterns:
- The journey was fragmented and non-linear
- Product awareness was strong individually, but brand cohesion was weak
- Onboarding, activation, and engagement often happened in isolation
- Developers didn’t realize Consensys tools could work together




Collaborating Through Workshops
We hosted two workshops to refine the journey map and explore next steps:
- Assumption-Busting Workshop: We invited a cross-functional team to critique the journey map and surface overlooked gaps or friction points.
- Solution Framing Workshop: We shifted focus from mapping to imagining what a more seamless, integrated experience could look like.
These workshops helped strengthen buy-in across teams and identified opportunities not only for product improvements but also for cross-product storytelling and packaging.
Validating with User Research
With a more complete journey map in place, Tyreek conducted qualitative research with developers to validate our assumptions and highlight areas for improvement. Key takeaways:
- Developers want toolchains that “just work together”
- Seamless integration is more valuable than just individual features
- Awareness of Consensys as a unified brand was still low
This validated our internal hypothesis and surfaced clear opportunities to simplify onboarding and deepen engagement across multiple Consensys tools.
Designing the Ideal Journey
Building on this, we mapped out an ideal developer journey—a path where Consensys tools are integrated into a clear, supportive ecosystem. We envisioned:
- Tools that hand off smoothly from one to the next
- Shared onboarding patterns and educational content
- More proactive product packaging for specific developer goals
We aligned this vision with internal frameworks like the DevU North Star metric and Matthieu Bouchaud’s growth loops for Infura—ensuring that we had measurable checkpoints along the journey and could design meaningful growth loops at each stage of the dApp lifecycle.
Sharing & Socializing the Work
We presented the journey map and ideal state to product leadership across Consensys, and made the work accessible internally to anyone interested. It now serves as a shared foundation for aligning roadmaps, product strategy, and marketing efforts across the developer experience.


Results & Impact
This project created a shared understanding across Consensys of how developers move through the Web3 ecosystem—and how our products can better support them.
Outcomes:
- A unified Developer Journey Map adopted across product, research, and marketing
- Integration opportunities identified across Infura, MetaMask, Truffle, and Linea
- Used as a strategic artifact in cross-functional planning and product packaging
- Guided by internal frameworks like DevU North Star and Infura growth loops
- Shared with product leaders and used in ongoing roadmap planning
This work laid the foundation for a more integrated developer experience and helped shift internal conversations from siloed tools to a holistic product ecosystem.