Opportunity statement
Github for Miro - Both platforms are popular amongst product teams but the lack of integration means manual effort, lost information and no source of truth. I designed this integration as a Miro app to seamlessly connect the two. It means product managers, designers, stakeholders, scrum masters and engineers can always maintain context and prevent outdated issues
Role - Product designer, product strategy, user flows, user research, design systems, pricing model, user experience, information architecture and interface design
Timeframe - Over 6 months
Listing - https://miro.com/marketplace/github-for-miro/
The agile truth
As our first time working with Miro, we faced hurdles around the feasibility, design and business decisions throughout the project.
For design, the challenges included
Limited design system existing yet
Strict design guidelines
Limited feasibility
Lack of access to some functionality
Here, an agile method shone through. We were able to develop an MVP in a short-time frame by combining testing, building and designing into the same sprints.
Research (discovery)
Discovery research encompassed desk research (empathy mapping & competitive analysis) followed by user interviews (5 x customer interviews globall)
Value Prop Canvas
Helps us think big picture, empathise with pain points, challenges and what relievers we can provide
Comp Analysis
We looked at competitors (non directly worked in what we were doing), as well as posting on forums to understand users
User interviews
Miro hooked us up with some customers who were looking for an integration like this, and I spoke to them over 45-min zoom sessions
Synthesis
All this research was synthesised for a user flower
The flow(s)
Building a user flow helps the engineers and stakeholders alike what the big picture is. It helps capture any edge cases.
It also highlights where challenges and pain points may lie and how we may reimagine the experience.
Starting from a high level miro flow, I follow with a more detailed figma flow.
Build & Test
Build & test are done in tandem in an agile environment to take advantage of our sparring.
After the first couple of iterations I use Maze until a demo link is ready to test with user the different flows.
The figma is constantly changing to adapt to this & we have weekly sparring meetings to review what goes into the backlog.
Usability test and its results during active sprints help me quickly discuss with engineers and my trio the feasibility of a particular feature, as well as highlighting any bugs that would stop the user.
Weekly sparring gives me a forum to spar with my squad on different matters relating to the overall user experience, as well as interface and UI audt.
Good relationship with my squad means we can communicate efficiently. This is coupled with well-organised files in my Figma and use of dev-mode which helps my engineers identify what to work on
Changes sometimes need to be made. There were instances where it was clear the UX wasn’t intuitive, so we would need to quickly pivot to a new design and adjust the flow
From design
To an app
And beyond
The bigger picture
Outside of the app design, I also drove the initiative to standardise the way we work with Miro as a company. This included design guidelines and check-out experience
