Honey started to have its most hyper-growth since 2019. With more ppl joining, staying scrappy, and breaking things were still sometimes valuable. On the other hand, the cost of NOT organizing was surging. We were in desperate need of standard processes to show us how to be aligned yet autonomous.
The team was still having multiple processes after the transition from Lean UX to Design Thinking. As a result, we started to have the wrong investment. Either too little in high importance project or the opposite. We needed a map to know When, What, and Who while working together.
I hold multiple listening sessions to understand all different styles of processes internally, from design/eng/product. I also studied what's out there externally(Lean UX, Design Thinking...). Then reviewed it across, up, and down.
In the end, we decided to modify the "double diamond" design thinking model to our own needs.
Due to the time limit, I only involved Eng and Product. More partners like analytics, QA, content strategy, marketing should be invited into the next iterations.
As the team grows, the scrappy way of tasking and tracking everything via Slack was no longer scalable. Tons of project management tools were out there. We chose Jira to save cost and have Product/Eng continuity. Additionally, how might we also bake the Product Development Process Map above into Jira?
The rest of the Jira artifacts, such as 'Issue template', 'Different issue types based on our different verticals', and 'Jira workflow'.
Honey has been planning annually and quarterly for years. Our design team has been excluded. As a result, we ended up overwhelmed and underappreciated, together with lots of last-minute requests and mediocre design quality. Most of the design team members surfaced this issue to their PMs, unfortunately, the bottom-up approach was not effective. When I stepped into the Head of Design role, this issue became one of my top priorities. So we can solve it from a top-down approach.
The proposed timeline with the Design joining:
Just like how the Product planned in one place and then demoed to the entire company. We started to use Miro as our single source of truth to plan and then to communicate to everyone within Honey Design.
The team has grown to the point where it was too big to run rituals together. We need to break it down into smaller pieces with aligned guidelines. So, each line manager could run it within its own design vertical. COVID was happening, it's needed more than ever.
After lots of listening sessions with my designers, design managers, and feature team peers, we came up with the weekly rituals plan as below:
Last but not least, everything was documented within Notion, from 1:1 to Monthly All Hands. Below is an example of how we run Weekly Warm-up in Notion.