This one shift in your "app audit" process will give you back your time
In a recent thread, we were discussing the overwhelm of having too many apps in your productivity stack and the importance of doing audits to streamline it. I was a strategic consultant for many years in the public, private, and non-profit sectors; here's the flow I used in week one with an org, vis-a-vis tackling the stack.
- Accept that your stack is not your system. In our early discussions, my clients almost always had recently licensed or were eager to license a new tool for the team to use to get organized. The first shift is a mindset one: a great tool doesn't create the process; it makes an existing process more effective. The apps aren't the key - clarity and optimization of process is.
- Define your process, not your stack. If you talk about your process in terms of the tech you use, switch the tools out. You don't "use Chat GPT" then "Google Docs" then "Outlook Calendar." You "brainstorm and reflect on possible paths forward," then "outline core steps," then "calendar step 1." This shift isn't just about being open to alternative tools. It's about examining the process itself for ways to optimize it. I conduct this app-to-process mapping with every team member to review what tools they use then uncover individual and shared approaches to getting things done.
- Go manual for 1-3 days. The next thing I'd do is take all of the toys/instruments of torture away (one team members' tech treasure is always another colleague's greatest aggravation). It's time for index card sticky notes and giant markers on a shared wall. All stand ups, goals, task assignments, and completion happen in front of this big, and sometimes ridiculous-looking, wall. Within three days, the critical team dynamic emerges. How do they share information? Ask for and receive help from leaders? Check in and prioritize next steps? With everyone working in the same space, and without the added friction of simultaneously navigating a tech tool, this can be as fast as the end of Day 1. It never takes more than 3 days - and by then, even the most techphobic team members are seeing tech solutions in a much better light.
- Document the process. Create a functional doc clearly detailing the ideal team workflow. Discuss it with the team - again, not in terms of specific apps but focused on their individual and shared approaches.
- Map the process back to tech. Get a list of every tool the team has access to (this might include a talk with IT at larger companies). Do the research to get familiar with every potential solution (trials, reviews, community, and IT's notes and sentiment from company usage). How can you enable the ideal process with as few panes of glass as possible? For me, it isn't about reducing the number of apps but the number of tabs and windows, the "context switching" it takes throughout a day's work. If there isn't a single solution in their stack - or available elsewhere - I've definitely built custom solutions, ideally integrating tools they already use. Low-code and no code made that much easier on my end years ago - and inspired me to build MIA (Managing Information Assets), my Microsoft 365-integrated HR talent acquisition app, now in its 6th year of an enterprise license.
- Train the team on the tech as it applies to their process. Extensive onboarding for tools can be daunting or exasperating. The team needs to replicate its workflows, not present the product at a tech conference. We transfer the sticky notes for continuity, then I work with them for at least two standups using the tool - after they happily rip the sticky notes off the wall.
In my Continuation reports, I document for everyone how to keep their process going AND growing. And I loop in IT, if they have one, to connect the stack to actual team functions. That way, if a tool goes down, a license is ending, or a new tool arises, they have a way to prioritize their own work in support of the team.
As you can imagine, after years of this work – and creating custom all-in-one apps in specific client spaces – I realized how mission critical it was to end the "tab tax" of constantly jumping through tabs, apps, and windows trying to get things done. With Korgi, the big aha was letting teams use their own apps and drives, from the world's leading productivity and collaboration tools, in a single shared space. We turn your stack into an app. And our users are turning all that reclaimed time into focus, scaling, and revenue.