Tech Lead Handbook
  • 👋Introduction
  • People
    • Space for Growth
    • One on Ones
    • Manage Conflicts
    • Deal with Passive Aggressive
    • Give Feedback
    • Performance Management
    • Manage Up
    • Talent Matrix
  • Engineering
    • Pair Programming
    • DCI Framework
    • Code Ownership
    • ADR
  • Leadership
    • Leadership Competencies
    • The Communication Pyramid
    • Anti Patterns
  • Prioritisation
    • Types of Decisions
    • Pros and Cons
    • Decision Matrix
  • Hiring
    • Hiring Process
    • Prepare a Hiring
    • Position Description
    • Shortlisting
    • Case Study
  • Product
    • Working with Product Managers
    • Assumptions Mapping
    • Decision Making
    • Practice vs Process
    • Nemawashi
    • OKRs
    • Consensus vs Consent
  • Project
    • The Triple Constraint
  • Strategy
    • Tech Strategy
  • Communication
    • Use Positive Language
  • Shortlist
  • ...
Powered by GitBook
On this page
  • The What
  • The How
  • Be more descriptive
  • Be less prescriptive
  • Be supportive
  • Process vs Chaos
  • Exceptions
  • Red Flags
  • Tips
  • Pitfalls
  • Refs
  1. Product

Practice vs Process

High-performance teams probably need both. When should you leverage Practice more? When should you rely on Process?

PreviousDecision MakingNextNemawashi

Last updated 1 year ago

The What

Practice: flexible & continuous improved ➡ innovation

Process: well-defined & repeated steps that achieve a predictable result ➡ operation

The How

Be more descriptive

  • Give them a problem

  • Provide more context

  • Explain the WHY

Be less prescriptive

  • It is hard to document unknownor uncertain things

  • It is awesome to give the team a problem to solve ❤️

  • It is great to give the team a solution to implement 😀

  • It is ok to give the team implementation instruction 👌

Be supportive

  • Encourage your team to talk to people if there are questions

  • Encourage your team to support each other and recognise their supports

  • Bring some certainty to your juniors to reduce their anxiety

Process vs Chaos

  • Chaos isn't always a negative thing. It can be important for innovation.

  • Process improves operational efficiency for repetitive workflows

  • Know how to live in an environment that may have some chaos

  • Deal with tight deadlines

  • Developers have to attend lots of meetings

  • A small team has a heavy process

  • Give a fish if you absolutely have to

  • How to fish whenever you can

  • High potentials only need some hints

  • Write an essay on the Trello card or Jira ticket

  • Your task like an IKEA assembly instruction

Refs

Exceptions

Red Flags

Tips

Pitfalls

✅
🔴
📜
🕳️
High-performance team-building in the future of work