Christine Phu

How to pick the right tools for your team

Finding the right tools for your team isn’t easy. You need to have a mix of strategy, rational decision making, good judgement and some intuition.

In this guide, you’ll learn how to pick the right tools for multiple teams and get buy-in. We’ll walk through how to:

Navigation

  1. Identify the problem.
  2. Measure the problem.
  3. Convince leadership.
  4. Get a team of workflow experts together from each team.
  5. Research and test tools.
  6. Present the tools.
  7. Pick the tool.

📂 Resources

🚫 This guide doesn't include:

  • Implementation
  • Change management and adoption
  • Post-implementation and continuous improvement

🎯 This guide works best for:

  • Companies with 100+ employees
  • 2+ teams to find tooling for
  • Companies with a procurement process

When I was a data analyst in working in professional services, we had to jump between five tools just for the project intake. Some of the tools were glitchy or we didn’t have the right permissions. This is a pain point for many teams leading to frustration, bitterness, delays and mistakes.

If you don’t have a good tool stack, it’ll cause inefficient processes and scattered tools. The operational debt builds up and affects everything that’s built on top of it. Having a good tool stack gives you a solid foundation to build processes on.

Now that I’m in a position to make tooling decisions, I make it a priority to pick the best tool for the teams I’m supporting. Here’s how.


1. Identify the problem

Imagine you’re an implementation manager and you’re looped into a potential project.

By the time project intake is over, you’ve gone through six tools, three teams, and two weeks has passed — and this doesn’t even include the dreadful invoicing part.

You go through this for every project and it’s extremely frustrating. This is how you identify problems.

Frustration is a tool if you learn to use it rather then descending into anger and hopelessness.

Identify problems as an individual contributor:

  1. Notice how you’re feeling as you’re going through certain processes.
  2. Name the feeling — is it frustration? Anger? Hopelessness? Stress?
  3. Focus on the problem that’s causing the feeling. What exactly is causing the feeling? What would make things feel better?

Identify problems as a manager:

↑ Back to top

2. Measure the problem

When I was a solutions engineer, we didn’t have a process or the right tools for project intake, quality control, and deliverables. One project took 51 emails, 46 hours, and 4 teams to confirm the specs. Projects were consistently delayed, we made a lot of mistakes due to incomplete specifications, and had to re-do projects multiple times.

We feel these pains first-hand as the person doing the actual work, but how do we get the attention of management? This is where measuring the problem will help. Your manager will have to explain why this matters to their manager, and data can help when first-hand experience is missing. Measuring things will show managers the numbers, time to value, and the impact of the problem.

Things you can track:

↑ Back to top

3. Convince leadership

If multiple teams are involved, you’ll need to get buy-in from multiple leaders. If you can’t get buy-in, then you may be wasting your time researching tools.

You must convince leadership that:

Presentation Framework:

  1. Scope of the problem including the measurements
  2. Risks if we don’t do this
  3. Before and after
  4. Options, including any preliminary tooling research
  5. Limitations of our current solution and the affected teams
  6. Next steps

This is an example of a flowchart I made to show leadership our future if we stayed on the current path. I wanted to show them how unmanageable the problem will get.

Flowchart Example

This is an example of how I presented the limitations of our current process. I highlighted the biggest problems in red and only talked about those.

Limitations Example

↑ Back to top

4. Gather workflow experts

Once you get buy-in, it’s important to include stakeholders early. This gives them more skin in the game and will help later with procurement and adoption.

Who you should include:

↑ Back to top

5. Research and test the tools

Now here’s the fun part. Make sure you trial tools and don’t depend on only marketing content or sales people.

  1. Sign up for trials: Test the actual user experience.
  2. Use a weighted system: Have a non-biased way to assess tooling. Template here.
  3. Check Security & Integrations: Eliminate tools that don't meet protocols.

⚠️ Sales Red Flags:

Sometimes they will straight up lie to you. For example, if you’re looking for specific integrations, make sure they actually have it and it’s not just "on the roadmap."

↑ Back to top

6. Present the tools

Once you have the top 3 tools, it’s time to present them and have a discussion. Recap why you're doing this, summarize research, and break down the specifications of the top 3 (features vs workarounds).

Check out the Tools Overview - Top 3 presentation template.

↑ Back to top

7. Collect feedback & pick the tool

Gather everyone’s feedback into a centralized document. When picking, how detailed you want to get is up to you. Once the vote is finished, get an official quote with a line-item breakdown. Because of all the research you've done, you'll able to fly through procurement.

Final Tip

There will be compromises no matter what you choose. You can’t make everyone happy. The weighted system will help you decide which compromises have the least impact.

↑ Back to top

When you follow a strategy to pick the right tools, you’ll reduce operational debt for the company over time. Optimizing operations is an ongoing journey, and following this guide will set you on the right path. Give these methods a try and let me know how it goes!

And remember, the work doesn’t stop at tool selection. You’ll need to consider implementation and costs, change management and adoption, and continuous improvements.

How do you select tools at your company? I’d love to hear how others do it!

#work