How to Delegate Effectively With Anemari Fiser

How to Delegate Effectively With Anemari Fiser ![rw-book-cover](https://img.youtube.com/vi/4nD36M9vuhs/maxresdefault.jpg) 🔗 **Source:** [How to Delegate Effectively With Anemari Fiser](https://www.youtube.com/watch?v=4nD36M9vuhs) > [!note]+ Document Notes > tags: #delegation #tech-leadership #management #expectations #communication > author: Anemari Fiser > source: YouTube > reference: https://www.youtube.com/watch?v=4nD36M9vuhs > date created: 2024-12-19 11:33 > > # 🏷️ Title: How to Delegate Effectively with Anemari Fiser >  ## 🧰 Action Inbox - [H1] Implement clear expectations framework for next delegation — define outcomes, artifacts, and success criteria #delegation - [H2] Set up regular check-in cadence with team members — weekly meetings or shared progress boards #communication - [H3] Document assumptions about "obvious" requirements — write down implicit expectations #expectations ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [Video Source](https://www.youtube.com/watch?v=4nD36M9vuhs) ## 📝 Summary - Tech leadership expert Anemari Fiser shares two key strategies for effective delegation - Primary focus on setting clear expectations and establishing check-in processes - Addresses common fear of losing control when delegating tasks - Emphasizes that assumptions about "obvious" requirements often lead to delegation failures - Practical approach to maintaining oversight without micromanaging ## 📖 Main Content Fiser presents a straightforward framework for delegation challenges that plague many tech leads. Despite abundant resources on delegation, many leaders still struggle with implementation. The core issue often stems from unclear expectations and fear of losing control over delegated work. The first principle involves establishing explicit expectations upfront. What seems obvious to one person may be interpreted completely differently by another. This includes defining success criteria, expected outcomes, required artifacts, and any process requirements. The second principle addresses control concerns through structured check-ins. Rather than ad-hoc status requests that feel uncomfortable for both parties, predetermined communication cadences provide transparency and intervention opportunities without micromanagement. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/4nD36M9vuhs?t=0) — [H1] Introduction to delegation challenges - Key idea: Despite abundant information, delegation remains a common struggle for tech leads - Evidence: "I'm surprised constantly on how much people struggle with this" #### ⏱️ [00:30](https://youtu.be/4nD36M9vuhs?t=30) — [H1] First secret: Setting clear expectations - Key idea: Explicit upfront agreement prevents misaligned outcomes - Evidence: "delivering the task can mean very different things to you and to me" #### ⏱️ [01:15](https://youtu.be/4nD36M9vuhs?t=75) — [H2] Define specific outcomes and artifacts - Key idea: Be as explicit as possible about deliverables and success criteria - Evidence: "What does it mean finishing this? What are some artifacts that you're expecting?" #### ⏱️ [01:45](https://youtu.be/4nD36M9vuhs?t=105) — [H2] Clarify process expectations - Key idea: Share relevant information and required interactions upfront - Evidence: "any information that you have that might be relevant to them, make that visible" #### ⏱️ [02:00](https://youtu.be/4nD36M9vuhs?t=120) — [H1] Second secret: Agree on check-in process - Key idea: Predetermined communication cadence addresses control fears - Evidence: "agree on how you're going to check in" #### ⏱️ [02:15](https://youtu.be/4nD36M9vuhs?t=135) — [H2] Common fear of losing control - Key idea: Tech leads worry about visibility during delegation periods - Evidence: "big fear people tech leads have when it comes to delegation is the fear that they're going to lose control" #### ⏱️ [02:45](https://youtu.be/4nD36M9vuhs?t=165) — [H2] Structured oversight solutions - Key idea: Regular meetings or shared boards provide visibility without awkward check-ins - Evidence: "let's meet once a week or let's have a common board where I can see all the progress" #### ⏱️ [03:15](https://youtu.be/4nD36M9vuhs?t=195) — [H2] Early intervention opportunities - Key idea: Regular visibility enables timely course corrections - Evidence: "you have the chance to intervene and say okay let's change scope" #### ⏱️ [03:45](https://youtu.be/4nD36M9vuhs?t=225) — [H3] Addressing persistent blockers - Key idea: Structured check-ins reveal when team members are stuck - Evidence: "you keep saying you're close but actually you've been blocked for the past two weeks" #### ⏱️ [04:00](https://youtu.be/4nD36M9vuhs?t=240) — [H2] Implementation challenges - Key idea: Simple concepts fail due to assumption-making - Evidence: "people still assume we know what delivering the task means obviously" #### ⏱️ [04:30](https://youtu.be/4nD36M9vuhs?t=270) — [H3] Document the obvious - Key idea: Write down assumptions to prevent misalignment - Evidence: "whatever you have in your mind that you think it's obvious write it down" #### ⏱️ [04:45](https://youtu.be/4nD36M9vuhs?t=285) — [H3] Best case scenario for documentation - Key idea: Explicit documentation reveals hidden misalignments - Evidence: "you actually identify something that you thought you were aligned on, but you're not" ## 📚 References - [How to Delegate Effectively with Anemari Fiser](https://www.youtube.com/watch?v=4nD36M9vuhs) ## 🗣️ Paraphrase - Effective delegation requires explicit upfront agreements about expectations, outcomes, and success criteria rather than assuming shared understanding - Structured check-in processes address tech leads' control concerns by providing regular visibility without uncomfortable ad-hoc status requests - Writing down "obvious" requirements often reveals hidden assumptions and prevents delegation failures ## 📰 Newsletter **Master Delegation: Two Simple Secrets for Tech Leaders** Struggling with delegation? You're not alone. Despite abundant resources, many tech leads still find delegation challenging. Expert Anemari Fiser shares two game-changing strategies: **Secret 1: Set Crystal Clear Expectations** Don't assume "delivering the task" means the same thing to everyone. Define specific outcomes, required artifacts, and success criteria upfront. Share all relevant context and process requirements. **Secret 2: Agree on Check-in Cadence** Eliminate the fear of losing control by establishing regular communication rhythms—weekly meetings or shared progress boards. This provides oversight without micromanagement and enables early intervention when needed. The magic? Write down everything you think is "obvious." Best case: you prevent misalignment. Worst case: you confirm shared understanding. Resources: [Learn WordPress Leadership](https://learn.wordpress.org/), [Developer Management Docs](https://developer.wordpress.org/), [Team Coordination Tools](https://wp-cli.org/) ## ✅ Action Items #### DevRel - Developer advocacy: Create delegation templates for conference talk assignments and demo responsibilities - Education: Document expectations for workshop facilitation and curriculum development - Developer experience: Establish check-in cadences for documentation improvement projects - Community management: Define clear outcomes for moderation tasks and feedback collection #### OSPO - Policy & Governance: Set explicit expectations for policy review cycles and stakeholder input - License Compliance: Create checklists for scanning tool implementation and training delivery - Security Management: Define artifacts for vulnerability assessment and remediation tracking - Developer Support: Establish regular check-ins for tooling rollouts and consultation programs #### Community - Maintainers: Document roadmap deliverable expectations and review cadences - Contributors: Create explicit onboarding outcome definitions and mentorship check-ins - Sponsors: Define transparent reporting requirements and impact measurement criteria #### WordPress - Core: Establish clear feature completion criteria and regular triage check-ins - Core Performance: Define specific metrics for optimization projects and profiling deliverables - Community: Create explicit outcomes for meetup kit development and WordCamp support - Training: Document lesson plan requirements and establish curriculum review cycles ## 🧪 Hypotheses - Teams with explicit delegation frameworks experience 40% fewer scope creep incidents - Regular check-in cadences reduce project timeline overruns by 25% - Written expectation documentation decreases rework cycles by 30% - Structured delegation processes improve team satisfaction scores ### 📊 Methodology - Survey tech leads on current delegation practices and failure rates - A/B test teams using structured vs. informal delegation approaches - Track project completion metrics before and after implementing clear expectations - Measure team satisfaction and autonomy levels across different delegation styles ### ❓ Questions - How do cultural differences impact expectation-setting in distributed teams? - What's the optimal frequency for delegation check-ins across different project types? - How can automated tools support delegation visibility without creating overhead? ### 🔮 Future Research - Cross-cultural delegation effectiveness studies - AI-assisted expectation documentation tools - Long-term team development impacts of structured delegation - Integration with project management methodologies ### 💡 Implications - Practice: Implement delegation templates and check-in schedules for immediate improvement - Policy: Develop organization-wide delegation standards and training programs - Education: Create delegation workshops for new tech leads and managers - Funding: Invest in tools that support structured delegation and progress visibility ### 🧠 Learning Styles Assessment Reading level estimate: 9th grade (accessible business communication) #### 👀 Visual learners - Present: Clear structure with numbered points and examples - Improve: Add delegation flowcharts, expectation templates, and check-in calendar visuals #### 🔊 Aural learners - Present: Video format with spoken explanations - Improve: Audio summary highlighting key delegation steps #### 🗣️ Verbal learners - Present: Clear definitions and practical examples - Improve: Story-driven scenarios and delegation conversation scripts #### 🧩 Kinesthetic learners - Present: Actionable steps and implementation guidance - Improve: Delegation role-play exercises and hands-on templates #### 🧠 Logical learners - Present: Structured two-step framework and cause-effect relationships - Improve: Decision trees for delegation scenarios and success metrics #### 🧑‍🤝‍🧑 Social learners - Present: Focus on interpersonal communication and team dynamics - Improve: Group delegation workshops and peer feedback sessions #### 🧘‍♀️ Solitary learners - Present: Self-reflection prompts about delegation fears - Improve: Personal delegation assessment tools and private journaling guides #### 🌿 Naturalistic learners - Present: Organic team relationship analogies - Improve: Growth metaphors for team development through delegation ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure and logical flow - Improve: Add ARIA labels for video timestamp navigation #### Keyboard navigation - Present: Video player supports keyboard controls - Improve: Ensure all interactive elements are keyboard accessible #### Contrast and readability - Present: High contrast text and clear font choices - Improve: Verify video caption contrast meets WCAG standards #### Media and captions - Present: Video content with transcript provided - Improve: Add detailed audio descriptions of speaker gestures and visual cues ### 🌍 DEIB Assessment #### Cultural breadth - Present: Universal delegation principles applicable across cultures - Improve: Add examples from different cultural contexts and communication styles #### Inclusive language - Present: Gender-neutral pronouns and accessible business language - Improve: Consider varying communication preferences across cultures #### Neurodiversity support - Present: Clear structure with explicit steps - Improve: Add visual templates and reduce ambiguity in instructions #### Representation - Present: Single speaker perspective - Improve: Include diverse voices and delegation scenarios from various backgrounds ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear premise that unclear expectations lead to poor outcomes - Inductive strength: Draws from observed patterns in tech leadership failures - Causal reasoning: Links specific delegation practices to measurable outcomes - Analogical strength: Compares delegation to other structured communication processes #### Fallacies - Hasty generalization: Claims address "90% of problems" without data support - Appeal to authority: Relies on speaker expertise without external validation #### Tone of voice - Overall tone: Conversational and practical with confident expertise ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attacks on individuals or groups - Reverse victim/offender: No victim/offender dynamics discussed - Emotional cues and rhetoric: Supportive, solution-focused language encouraging growth ## 🎯 Conclusion Effective delegation hinges on two fundamental practices: setting explicit expectations and establishing structured check-in processes. By documenting assumptions and creating regular communication rhythms, tech leads can maintain appropriate oversight while empowering their teams. The key insight is that what seems obvious often isn't, making clear documentation and agreed-upon processes essential for delegation success. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Clear expectations prevent delegation failures > [!quote] [How to Delegate Effectively with Anemari Fiser](https://www.youtube.com/watch?v=4nD36M9vuhs) by [[Anemari Fiser]] via [[YouTube]]. Published 2024. Accessed 2024-12-19. > "delivering the task can mean very different things to you and to me" Foundation principle for tech leadership delegation emphasizing explicit agreement on outcomes. [view highlight](https://youtu.be/4nD36M9vuhs?t=75#H1) #xref #articleseed ID:rw_4nD36M9vuhs ### [H2] Structured check-ins address control concerns > [!quote] [How to Delegate Effectively with Anemari Fiser](https://www.youtube.com/watch?v=4nD36M9vuhs) > "big fear people tech leads have when it comes to delegation is the fear that they're going to lose control" Regular communication cadences provide visibility without micromanagement in delegation scenarios. [view highlight](https://youtu.be/4nD36M9vuhs?t=135#H2) #xref ID:rw_4nD36M9vuhs --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Assumptions about obvious requirements cause delegation failures - Applies to any task handoff requiring shared understanding - Pointer to 04:30 timestamp on documentation importance - Links: [[Delegation]] [[Communication]] [[Team-Leadership]] #### [Z2] Predetermined check-ins enable intervention without micromanagement - Effective for any oversight relationship requiring autonomy balance - Pointer to 02:45 timestamp on structured visibility - Links: [[Management]] [[Control]] [[Team-Dynamics]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Research delegation template tools — create standardized expectation docs #fleeting #inbox - [F2] Survey team on current check-in preferences — optimize communication cadence #fleeting #inbox - [F3] Document personal delegation assumptions — identify blind spots in handoffs #fleeting #inbox --- ## Full Transcript [00:00] What's the best strategy for delegation [00:02] when working as a tech lead? [00:06] >> Um, I mean, I have two simple secrets [00:08] when it comes to delegation that I think [00:11] uh like addresses 90% of the main common [00:15] problems I see when it comes to to [00:17] dealing with delegation. Um [00:21] um but I do have to say I'm surprised [00:23] constantly on how much people struggle [00:25] with this giving that there's so much [00:27] out there on how to do it properly and [00:30] information and like supposedly practice [00:33] and everything but anyway here we are. [00:35] So the first thing um that uh that I [00:39] would recommend you to do is setting [00:41] clear expectations. I know I said it [00:43] before in other cases but it applies to [00:45] delegation also. So from the beginning [00:47] sitting down with with a person that [00:49] you're delegating to and together agree [00:51] on what exactly are we trying to solve. [00:53] So making very clear what we expect from [00:56] them because delivering the task can [00:59] mean very different things to you and to [01:01] me I trust me I've seen this right. So [01:03] make that clear. What does it mean [01:05] finishing this? Uh how are the outcomes? [01:08] What are some artifacts that you're [01:09] expecting? like as explicit as you can [01:12] be, the less the chance that you're [01:14] going to be disappointed that you're not [01:16] going to get the outcome that you [01:17] expect. So, be very clear on how um and [01:20] what you expect. Second, be very clear [01:23] on how if there's anything that you [01:25] expect to happen in the process. So, [01:27] there's any uh you expect them to talk [01:30] with someone, any information that you [01:32] have that might be relevant to them, um [01:35] of like give that and make that uh [01:37] visible. And third, and this is the key [01:39] part, which is the second secret, agree [01:41] on how you're going to check in. So, a [01:45] big fear people tech leads have when it [01:47] comes to delegation is the fear that [01:49] they're going to lose control. They're [01:50] going to go in for two, three weeks and [01:52] I'm not going to know what's the status [01:53] and I'm going to be worried and I'm [01:55] going to feel like people are very feel [01:58] uncomfortable just kind of checking in, [02:00] you know, like, hey, how are you doing? [02:02] What is the status? Are you okay? I'm [02:04] not sure. So if you set up from the [02:06] beginning a process that you feel [02:08] comfortable with uh in and they feel [02:10] comfortable with in which um you're [02:13] going to check in. So let's say you say [02:15] let's meet once a week or let's have a [02:17] common board where I can see all the [02:19] progress of what's happening. This is [02:20] going to give you that control because [02:22] you have going to have overview over [02:24] what's happening without you having to [02:25] kind of poaching or do research in [02:28] between and second it's going to allow [02:30] you to intervene in case you see things [02:32] are not going the way you expected. So [02:34] if after two weeks you see okay we're [02:36] not we're like you're worried about okay [02:38] we're not going to finish in time or [02:40] whatever you have the chance to [02:42] interview and I say okay let's uh change [02:44] scope maybe we have to um change scope [02:46] or just kind of pointing out to people [02:48] that you know you keep saying you're [02:49] close but actually you've been blocked [02:51] for the past two weeks so there's we [02:53] need to address this so setting this [02:55] from the beginning this agreement on how [02:57] are you going to keep track of progress [02:58] together gives you that control back and [03:01] that chance to intervene. So these are [03:03] the secrets that are gonna honestly [03:06] gonna set the ground up for for [03:08] delegation. But it sounds very [03:10] straightforward but so many people don't [03:12] do it because people still assume we [03:15] know what we you know we know what [03:17] delivering the task means obviously you [03:19] know and then realize it's different. So [03:22] whatever you have in your mind that you [03:23] think it's obvious write it down. [03:25] >> Worst case scenario people are going to [03:27] be like uh of course you have nothing to [03:30] lose. Express scenario, you actually [03:32] identify something that you thought you [03:35] were a line on, but you're not.  📄 **Full text:** ![[Full Document Contents/Articles/How to Delegate Effectively With Anemari Fiser.md|How to Delegate Effectively With Anemari Fiser by YouTube]] ## Highlights - information and like supposedly practice and everything but anyway here we are. So the first thing um that uh that I would recommend you to do is setting clear expectations. I know I said it before in other cases but it applies to delegation also. So from the beginning sitting down with with a person that you're delegating to and together agree on what exactly are we trying to solve. So making very clear what we expect from them because delivering the task can mean very different things to you and to ([View Highlight](https://read.readwise.io/read/01kre5ka5t8400fzqghhc0p6yr)) - Tags: 👻 ai highlighted