> For the complete documentation index, see [llms.txt](https://jamiewen00.gitbook.io/tech-lead-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jamiewen00.gitbook.io/tech-lead-handbook/product/practice-vs-process.md).

# Practice vs Process

## The What

**Practice**: flexible & continuous improved ➡ innovation

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

![](/files/-Mi_aZs7Ew92BsMn_WjW)

## The How

### Be more descriptive

* Give them a problem
* Provide more context
* Explain the WHY

### Be less prescriptive

* It is hard to document `unknown`or `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

## :white\_check\_mark: Exceptions

* Deal with tight deadlines

## :red\_circle: Red Flags

* Developers have to attend lots of meetings
* A small team has a heavy process

## :scroll: Tips

* Give a fish if you absolutely have to
* How to fish whenever you can
* High potentials only need some hints

## :hole: Pitfalls

* Write an essay on the Trello card or Jira ticket
* Your task like an IKEA assembly instruction

## Refs

* [High-performance team-building in the future of work](https://www2.deloitte.com/xe/en/insights/focus/technology-and-the-future-of-work/high-performance-team-building.html)