How to identify and build scalable processes
Teams have to adapt their way of working as companies grow, but ... how do they efficiently collaborate and communicate when 1:1 conversations can't always happen?
When new hires can't sit next to tenured team members or subject matter experts aren't available to answer questions, teams need solutions to ensure they are efficiently communicating and collaborating as they grow. The answer? Scalable processes.
Learn how to identify, build, and manage scalable processes to support your team through growth.
🚀What is a process?
A process is a streamlined approach to a solving a problem.
Designs for the true, underlying problem - a process is the opposite of a patchwork solution
Includes repeatable actions
Requires set up and adoption from the top-down AND bottom-up
✨ How can you make one?
Identify cracks in communication
What information are people struggling to get fast?
What repeat conversations are people having?
What is being typed in Slack, Email, Microsoft teams, etc, that doesn't require a unique response?
Who owns the information connected to the questions above?
Design for the long-term
Where does the breakdown begin? In other words, where does your process have to start to get at the root of the problem?
Who is the audience? What person/role type will benefit from this process?
What do we need from the person who owns the information to inform a better process?
How can we make sure no one needs to type this answer ever again?
Set up a more efficient workflow
How can we get the audience of this process the information they need at the right time?
How can we get the audience the answers they need, BEFORE they reach out to the subject matter expert?
How can we support the subject matter expert with documentation when repeat questions come their way?
How can we use dashboards, templates, automation (Zapier) to our advantage?
How will we account for edge cases (e.g., what experiments do we need to test)?
Drive adoption top-down and bottom-up
Top-down = new-hire training, company-wide meetings, by example (?)
Bottom-up = content jams, word of mouth, desperation to complete a task efficiently (!)
Measure and communicate efficiency
How are we gathering qualitative feedback?
What quantitative efficiency metrics do we care about related to this process? How will we measure those to record how the process is working?
How will we share out results to the team to communicate the benefits of the process and increase adoption?
Repeat & Iterate
How will we iterate on the process depending on people's feedback and metrics of success?
Does this process work? What are the points of breakdown that need to be addressed?
Where are people struggling to adopt the process?
Repeat :)
Card by: