Leadership

Problems Welcome. Solutions Required.

Oct 30, 2024

A hand holds a Rubik’s cube with the phrase “FIGURE IT OUT” on its side.

“In the middle of difficulty lies opportunity.” —Albert Einstein

As leaders in the tech industry, before all else, we’ve faced a situation where someone says, “Hey, there’s a problem.” It’s admirable that engineers spot problems, but always being the problem solver can slow down progress and hold back team development. Let’s look into a way to make problem-solving more efficient and effective while lifting team spirits, minimizing burnout, and sparking creativity.

The 1-3-1 Method

  • 1️⃣ One Clear Problem: Encourage your team to define the issue precisely.

  • 3️⃣ Three Possible Solutions: Have them brainstorm three viable options.

  • 1️⃣ One Recommendation: They analyze the options and present a well-considered choice.

What Changes When You Use It

  • Benefits for Managers: The 1-3-1 method reduces decision fatigue by providing thoughtful solutions, saving time and energy. It fosters strategic thinking among team members, allowing you to focus on higher-level strategies. It also enhances innovation through diverse ideas you might have yet to consider.

  • Benefits for Team Members: This approach increases ownership, engagement, morale, and cohesion. It reduces burnout by distributing problem-solving responsibilities and encourages skill development in critical thinking and decision-making.

Two Problems, Two Outcomes

Example 1: Deployment Delays

1️⃣ Problem: “Deployments are delayed by 45 minutes, affecting schedules and client satisfaction.”

3️⃣ Solutions:

  1. Optimize Build Scripts: Improve efficiency.

  2. Streamline Automated Testing: Remove redundancies.

  3. Implement Incremental Deployments: Deploy smaller chunks more frequently.

1️⃣ Recommendation: Optimize build scripts for immediate impact with minimal risk.

Outcome: Deployment times reduced by 30% in two weeks. Team morale improved as members saw tangible results.

Example 2: Customer Support Efficiency

1️⃣ Problem: “Customer response times have increased, decreasing satisfaction ratings.”

3️⃣ Solutions:

  1. Automate Common Responses: Use AI chatbots for FAQs.

  2. Adjust Support Staff Schedules: Reallocate during peak hours.

  3. Implement Ticket Prioritization: Focus on high-impact issues first.

1️⃣ Recommendation: Implement ticket prioritization to improve efficiency without extra resources.

Outcome: Customer satisfaction improved within a month; the support team felt more effective and less overwhelmed.

When Teams Push Back

Implementing the 1-3-1 method may face hurdles like resistance to change or difficulty defining obvious problems. Address these by leading by example—use the technique yourself and share success stories. Coach your team on framing specific issues, and emphasize that investing time upfront saves more in the long run by preventing misdirected efforts.

Making It Work for Remote Teams

Leverage collaborative tools like Slack or Miro for brainstorming. Schedule meetings considering different time zones to include everyone. Document everything in shared folders for transparency.

How to Start Monday

  1. Introduce the Concept: Discuss it in your next team meeting.

  2. Provide Resources: Offer templates or examples.

  3. Set Expectations: Encourage its use for upcoming problems.

  4. Celebrate Successes: Share wins resulting from the process.

Remember, outstanding leadership is about more than having all the answers. It’s about empowering your team to find them and fostering a collaborative environment where everyone thrives.

Let’s talk about your platform challenge.

If your organization is navigating scale under regulatory complexity—or making the shift from reactive delivery to resilient platform engineering—I’d welcome the conversation.

3. Nashville Skyline
1. Nashville Skyline
3. Nashville Skyline
1. Nashville Skyline
3. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline

Let’s talk about your platform challenge.

If your organization is navigating scale under regulatory complexity—or making the shift from reactive delivery to resilient platform engineering—I’d welcome the conversation.

3. Nashville Skyline
3. Nashville Skyline
3. Nashville Skyline
3. Nashville Skyline
3. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline

Let’s talk about your platform challenge.

If your organization is navigating scale under regulatory complexity—or making the shift from reactive delivery to resilient platform engineering—I’d welcome the conversation.

3. Nashville Skyline
1. Nashville Skyline
3. Nashville Skyline
1. Nashville Skyline
1. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline
4. Nashville Skyline
2. Nashville Skyline