Parrit
Open-Source Tool for Engineering Pairs
Product Designer + Product Manager
Product Discovery, Validation and MVP Launch
PROBLEM SPACE
Manual Pairing Boards
Fun yet how do you know what happened last week?
This team started with whiteboard, then moved to spreadsheet.
BUY-IN
Proof of Concept
The proof of concept met user needs but was hard coded for one team and had bugs.
LEAN RESEARCH
Alignment upon what to validate
Started by brainstorming assumptions.
Mapping assumptions about user needs to prepare for user research.
Who is primary user?
Does POC meet the needs of more than one team?
Especially larger teams?
HYBRID METHODS
Open-ended + Usability SESSION
To remain lean, tried out using an online tool for synthesis and analysis, See Board >
ASSERTIONS
Validated PersonA Breakdown
Fred is the primary persona yet two others were outlined to validate in future research, See More >
TOP INSIGHTS
Deciding on pair rotations is generally a quick decision making process because it needs to happen at the beginning of the day, directly after project team stand-ups.
It is important to keep track of pairing history to ensure newness of pairs but on large project teams it is difficult to remember past pair rotations.
IDENTITY
Logo Design exploration
We let the project team and a consensus of feedback from passersby determine the design, See Moodboard >
DESIGN
Sketching the Experience
Whiteboarding our solution before heading into Sketch.
LAYOUT + INTERACTIONS
wireframes For Story Writing
PRODUCT MANAGEMENT
User-first prioritization
We built up a backlog for engineers to pick up when they have time, See Pivotal Tracker >
VISUAL DESIGN
building a PARRIT brand
Our research highlighted desktop as primary use and phone for secondary users.
MVP
Product Launch to All Employees
Â
Company-wide email blast led to complications:
âž¡ 333 new users in first few hours
âž¡ Crashed our free PWS account
âž¡ Plus attracted legal concern!
Â
METRICS
Data Collection FOR KPIs
Snapshot from a few months post-launch in preparation for tech talk, looking at one-month period.
ADOPTION
lunchtime Tech Talk
Continued Contribution to Open-Source
MAINTENANCE
From project to Community
Parrit app continues to be iterated upon with code base available on GitHub.
We collaborate over Slack plus take feedback from users through a Help channel.
PRODUCT
Cross Synthesizing Feedback & Issues
We cross synthesized survey feedback with GitHub Issues six months post-launch, See Board >
Continuing to maintain our backlog on Pivotal Tracker.
GROWTH
Analyzing metrics to validate use
CONTINUITY
Need for creating a design system
An engineering contributor wanted to push this live.
We moved our design assets to InVision because some developers did not have access to Zeplin, Check it out >
INTERFACE
Refinements, New Features & Planning
