> 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) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://jamiewen00.gitbook.io/tech-lead-handbook/product/practice-vs-process.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.