Your Guide on How to Calculate Employee Retention Rate
Your employee retention rate affects your business’s bottom line & productivity. Learn how to calculate & improve it.
Meet Josh, Katya, and Brooke - part of an incredibly skilled and busy product team. Managing everything..
Meet Josh (Chief of Product), Katya (Sr. Product Manager), and Brooke (Product Designer) - part of an incredibly skilled and busy product team. Managing everything from bugs to feature design to overall strategy means there is little time for manual processes and tools that provide niche value.
We asked them about their experience with Flows and what has changed about their workflow.
1. What Flow have you found to be the most useful?
J: Idea Management -- sourcing good ideas within an organization can/should come from anywhere. Gusteau from Ratatouille said it best, “Anyone can cook.” but in this case, anyone can have an idea. No reason to miss out on that.
K: Our sprint retrospective flow has been super effective for our team. It has allowed us to significantly cut down on our meeting time by collecting the team’s feedback ahead of time and providing more structure during the meeting. It also creates another opportunity to recognize and reward teammates that have been especially helpful or amazing in the sprint.
B: I love our Product Feedback flow. It allows our team to gather and analyze feedback from internal stakeholders before moving forward with important design decisions. Having a quick and succinct way to do this saves a lot of time in meetings since we’re able to temperature-check new designs and features before putting time on the calendar.
2. What have you been able to automate that was manual before?
J: My one one-on-ones -- collecting the information was pretty manual and took a lot of time. Not only am I saving time, but I’m also getting better answers that I can look back on. In the past, I’d write shorthand and have a hard time going back through my notes.
K: Sprint retrospectives and daily standup -- these flows have been a great supplement to our daily standup and sprint retrospective meetings. They provide a standardized and measurable record of everything we’ve worked on and/or discussed and create a more flexible alternative when someone is unable to attend any of the meetings.
B: We also automated our weekly Product Sync to set agendas and take meeting notes - it allows us to keep meetings focused by pre-planning, and it lets us define and reference clear action items coming out of it.
3. How do you use Flows every day?
J: Daily standup is amazing. It’s really nice to see what the team is up to.
B: As Josh said -- I use our Daily Standup flow every day to make sure I understand our progress as a team, and it also helps me keep track of my action items for the day to hold myself accountable to reaching our team's goals.
K: Three’s a crowd! Daily standup is an integral part of our workflow. I also really love our bug hunt flow that provides a space for anyone in the company, particularly outside of the engineering team, to report any bugs they find. It serves as a great medium between scattered Slack conversations about bugs and allowing anyone to directly report bugs into Jira. We have standardized all details required for a proper bug report in this Flow, and I use that information to either validate the issue and create a bug ticket in Jira, or close the issue if it is already a known/logged issue or not a valid issue at all.
4. What tools have you been able to replace with Flows?
J: We’re now able to replace our survey tool and do surveys directly in Assembly. We used to use a standup tool to collect information. Now we do it directly in Assembly as well.
K: Using Confluence to track retrospectives. I also used to collect GIFs from the team to describe how the sprint went for them (a really fun addition to our retrospectives) and put them into a deck. Using flows for retrospectives allows me to collect valuable feedback on each team member’s sprint, have some fun with their GIFs for the sprint, and a relevant space to recognize and reward their teammates.
B: We’ve gotten rid of tools from recognition to retrospective, and now they all live within Flows.
5. What would your advice be to other product teams considering Flows?
K: Flows will not only provide you with the ability to build almost any tool, but it houses all of your tools and important information in one place. It’s pretty astonishing how much time you can waste in meetings without structure; flows will save you time (and money). Not to mention you still get Assembly’s signature platform of recognition which can be woven into any of your flows, providing countless opportunities to give praise and keep your team motivated.
B: My advice would be to go for it! Assembly is so flexible -- it works for tried and true processes, but it also gives you space to get creative. Take advantage of the inherently social nature of Assembly to foster valuable ideas and productive conversations.