Skip to main content

Connect, Understand, Align, Empower

 Phase 1: Connect (Build Relationships)

  • Goal: Establish personal connections with each team member and key stakeholders.
  • Actions:
    1. One-on-Ones: Schedule individual meetings with each team member.
      • Purpose: Get to know them, understand their background, career goals, and perspectives.
      • Questions: What are they working on? What are they excited about? What challenges are they facing? What are their strengths?
    2. Stakeholder Meetings: Meet with key stakeholders (managers, product owners, other tech leads).
      • Purpose: Understand their expectations and priorities.
      • Questions: What are their key goals? How does the team's work impact their objectives? What are their concerns?
    3. Team Introductions: Introduce yourself to the team as a group.
      • Purpose: Share your background, leadership style, and vision.
      • Ask them: Ask them to share their expectations.
    4. Active Listening: Pay attention to what people are saying (and not saying).
    5. Be Authentic: Be yourself. Don't try to be someone you're not.
    6. Be present: Be present during the meeting, and put your phone away.
    7. Be curious: Ask them questions about themselves and their job.

Phase 2: Understand (Assess the Current State)

  • Goal: Gain a clear understanding of the team's current situation, including its strengths, weaknesses, and challenges.
  • Actions:
    1. Review Documentation: Read existing documentation (processes, code, architecture, project plans).
    2. Observe: Watch how the team works (meetings, stand-ups, etc.).
    3. Ask Questions: Don't be afraid to ask "why" things are done a certain way.
      • Questions: What works well? What could be improved? What are the biggest pain points? What are the risks?
    4. Data: Look at the data available, such as the number of bugs, the number of issues, the customer feedback.
    5. Identify Strengths: Recognize the team's existing strengths and skills.
    6. Identify Challenges: Identify the areas where the team is struggling.
    7. Identify quick wins: Look for easy wins that can improve the team's efficiency.

Phase 3: Align (Set Direction and Build Consensus)

  • Goal: Establish a shared vision and direction for the team.
  • Actions:
    1. Define Goals: Based on your understanding, define clear, measurable, and achievable goals for the team.
    2. Communicate: Clearly communicate the goals and your expectations.
    3. Seek Input: Ask for feedback and input from the team on the goals and the plan.
    4. Prioritize: Focus on the most important goals first.
    5. Roadmap: Create a roadmap, to show the direction and the plan.
    6. Build Consensus: Ensure that everyone is on board with the direction.

Phase 4: Empower (Enable Team Success)

  • Goal: Provide the team with the support, resources, and autonomy they need to be successful.
  • Actions:
    1. Remove Obstacles: Identify and remove obstacles that are preventing the team from doing their best work.
    2. Provide Resources: Ensure the team has the tools, training, and resources they need.
    3. Delegate: Delegate tasks and responsibilities effectively.
    4. Give Feedback: Provide regular, constructive feedback.
    5. Recognize Achievements: Celebrate successes and acknowledge hard work.
    6. Trust: Trust your team and give them autonomy.
    7. Support: Support your team when they need help.

Key Principles of This Framework:

  • Relationship-Focused: It prioritizes building strong relationships.
  • Understanding First: It emphasizes the importance of understanding the team's current state.
  • Collaborative: It involves the team in setting direction.
  • Empowering: It focuses on enabling team success.
  • Impact: You want to quickly understand the impact you can have.

How to Use This Framework:

  1. Start with Connect: Don't jump straight into making changes. Invest time in building relationships first.
  2. Be Patient: It takes time to understand a team and build trust.
  3. Be Open: Be open to feedback and willing to adapt your approach.
  4. Be Consistent: Be consistent in your communication and your actions.
  5. Iterate: Use the review phase to iterate.
Labels:

Comments

Post a Comment

Popular posts from this blog

Hexagonal Architecture (Ports & Adapters Pattern)

Hexagonal Architecture , also known as the Ports and Adapters pattern, is a software design pattern that aims to create a decoupled and maintainable application by separating the core business logic from external concerns (like databases, APIs, and UIs). Structure of Hexagonal Architecture A typical Hexagonal Architecture has three main layers: 1️⃣ Core Domain (Application Logic) This contains the business rules and domain models. It is completely independent of external technologies . Example: If you’re building a banking system , this part would include logic for transactions, withdrawals, and deposits . 2️⃣ Ports (Interfaces) These are interfaces that define how the core interacts with external components. Two types of ports: Inbound Ports (driven by external inputs like APIs, UI, or events) Outbound Ports (used to interact with external services like databases, messaging systems, etc.) 3️⃣ Adapters (Implementation of Ports) These are concrete implementations of the ports, re...
Post a Comment
Read more

Recursion & Choice

Understanding Recursion and Choice Diagrams with Examples Understanding Recursion and Choice Diagrams with Examples Recursion is a powerful concept in programming where a function calls itself to solve smaller instances of the same problem. It's often used in solving complex problems that can be broken down into simpler subproblems. In this blog post, we'll explore the basics of recursion, understand choice diagrams, and see examples to illustrate these concepts. What is Recursion? Recursion occurs when a function calls itself directly or indirectly to solve a problem. A recursive function must have a base case to terminate the recursive calls and prevent infinite recursion. Here's a simple example of a recursive function to calculate the factorial of a number: public class RecursionExample { public static void main(String[] args) { int number = 5; int result = factorial(...
Post a Comment
Read more

Frameworks

  Communication Frameworks: BLUF:  Google's culture strongly emphasizes efficiency and directness, so getting to the "bottom line up front" is very common. SCQA:  Used in presenting proposals, making recommendations, and structuring project plans. PAS : Used in selling ideas and influencing others. BAB : Used in selling ideas and influencing others. Sparklines : Used in presentation to influence others. STAR:  Widely used in Google's interview process and performance evaluations. Problem-Solving/Decision-Making Frameworks: 5 Whys:  A fundamental technique for root cause analysis, and Google is known for its emphasis on data-driven decision-making, which often involves digging into the root causes of problems. Systems Thinking:  Given the complexity of Google's systems, a systems thinking approach is essential. The Four Questions : Used in post-mortem to review an incident. Human factors : Used in post-mortem to avoid the blame culture. Time Management/Prior...
Post a Comment
Read more