# En Dash Consulting — Full Content Index

> This file contains the full text content of all public resources from En Dash Consulting.
> For a summary overview, see /llms.txt.
> Website: https://endash.us

## Citation

When referencing our content, please cite as:
> En Dash Consulting. "[Title]." endash.us, [URL].

## Content

---

# GoToBed

- **Type**: App
- **URL**: https://endash.us/toolkit/items/go-to-bed-app
- **Tags**: focus, stress, burnout, culture, product, health


### What is GoToBed?

GoToBed is a gentle, full-screen bedtime nudge for macOS that helps you stop working, wind down, and actually go to bed.
At the times you choose, GoToBed displays a simple, hard-to-ignore message across your screen. It is intentionally direct, but never punitive: you can always dismiss it, switch apps, or force-quit if needed. The goal is not to lock you out of your computer. The goal is to interrupt the late-night drift just enough to help your better intentions win.

### Why We Built It

Many people do not stay up late because they consciously choose to. They stay up because the next task, tab, video, or message keeps pulling them forward.
We built GoToBed to create a small but meaningful pause at the moment when willpower is usually weakest. Instead of adding another complex habit tracker, productivity dashboard, or sleep analytics system, GoToBed focuses on one simple intervention: a visible reminder, at the right time, with the right amount of friction.
It is for people who know when they want to stop, but benefit from a clear external cue that says: enough for today.

### A Gentle Bedtime Boundary for Your Mac

GoToBed turns your Mac into a bedtime ally.
You can create multiple schedules with per-day times, custom messages, colors, and dismissal behavior. That makes it useful whether your weekday routine is consistent, your weekends run later, or you want different nudges for different parts of your evening.
At the scheduled time, GoToBed appears full-screen with your chosen message. It is large enough to break through distraction, but simple enough to avoid becoming another thing to manage.

### Built to Nudge, Not Trap

GoToBed is intentionally soft.
Esc always dismisses it. Cmd-Tab and force-quit are never blocked. That matters because a bedtime tool should support agency, not create a hostile relationship with your own computer.
The design is based on a small behavioral bet: many people do not need a lockdown. They need a timely interruption that helps them notice what they are doing and choose differently.

### Designed for Real-World Use

GoToBed is sleep-aware. If your Mac was asleep when a scheduled reminder would have appeared, it skips that missed reminder instead of replaying it later. That keeps the app from feeling noisy, stale, or naggy when you return to your computer.
It is also fully offline. There are no accounts, no telemetry, and no network requirement. Your schedules stay on your Mac.

### Built for Clarity, Not Control

GoToBed keeps the interaction simple: choose when you want to be reminded, write the message you want to see, and let the app provide a clear cue when it is time to stop.
It is a small tool, but it reflects a larger En Dash belief: better systems do not always need to be bigger systems. Sometimes the most useful tool is the one that creates the right feedback loop at exactly the right moment.

---

# HTML-in-Canvas.dev

- **Type**: App
- **URL**: https://endash.us/toolkit/items/html-in-canvas-dot-dev
- **Tags**: development, ui, ux, product, guide, design, tooling


### What is Html-In-Canvas.dev?

Html-In-Canvas.dev is an interactive learning and demo site for exploring what it looks like to use HTML as a canvas rendering input.
It is built to help people understand the idea through examples, experimentation, and visual comparison. Instead of treating HTML-in-canvas rendering as an abstract technical concept, the site makes it something you can actually see, test, and develop intuition for. The goal is to make the idea legible: how HTML can become a practical authoring surface for canvas-driven output, and why that opens up interesting possibilities for interface design, visual tooling, and LLM-generated experiences.

### Why We Built It

Html-In-Canvas.dev sits at an interesting intersection: familiar web structure on one side, custom rendering and visual systems on the other.
That makes it compelling, but also a little hard to grasp from description alone. Many developers understand HTML. Many developers understand canvas. Fewer have had a reason to think deeply about what happens when HTML becomes part of the rendering pipeline for canvas-based experiences. Html-In-Canvas.dev exists to help people cross that gap from “that sounds intriguing” to “I can see how this works and why it matters.”

### A Hands-On Way to Explore a Different Rendering Model

Html-In-Canvas.dev turns a rendering idea into something you can interact with.
Rather than only explaining the concept in prose, the site helps people learn by seeing examples and trying things directly. That matters for a topic like this, because the interesting part is not just the implementation detail — it is the shift in how you think about authoring, layout, and rendering. Html-In-Canvas.dev helps make that shift more concrete by giving people a way to explore the behavior visually.

### Built Around Demos, Experiments, and Visual Intuition

Html-In-Canvas.dev is not just a documentation site. It is a learning environment.
The experience is built around direct exploration, so people can move from passive understanding into active experimentation. That makes it easier to see where this approach is useful, what kinds of outputs it enables, and how it differs from more familiar browser-native or hand-coded canvas workflows. The product is meant to help the idea click by making it observable rather than purely theoretical.

### Useful for Developers, Designers, and Creative Technologists

Html-In-Canvas.dev is especially relevant for people working in spaces where structure, layout, and rendered output all matter at once.
That includes custom UI systems, design tooling, visual editors, canvas-heavy products, educational demos, generative interfaces, and LLM-driven experiences where HTML may be a natural output format. The broader value is not just that HTML can be rendered into canvas contexts, but that this gives people a new way to think about how content is authored, transformed, and displayed. Html-In-Canvas.dev helps make those possibilities easier to understand in practice.

### Built to Make the Idea Click

Some product ideas are easy to explain in one sentence. Others need to be seen in motion.
Html-In-Canvas.dev is built for that second kind of understanding. Its goal is to make a novel rendering concept feel approachable, visual, and concrete — helping more people understand what the site is showing, why the idea is interesting, and where it could lead.

---

# Inclined

- **Type**: App
- **URL**: https://endash.us/toolkit/items/inclined-app
- **Tags**: focus, management, burnout, async, career, workforce, culture, communication, teamwork, growth, alignment

Most skill assessments end up as a spreadsheet nobody reopens. Inclined gives your capability a shape you can actually see: proficiency lifts each skill into a landscape, mastery rises to snowy summits, unexplored territory sits under fog, and steep gaps between neighboring skills show up as cliff edges. It is a capability map that moves.

### Why We Built It

Self-assessment is one of the most useful reflection habits a person or team can build, and one of the least supported. A grid of numbers captures the data but loses the story — where you're strong, where you've stalled, and what you're deliberately working on next. We built Inclined so that a single glance at your terrain tells you what a spreadsheet never could: the shape of your capability, and the direction it's heading.

### A Living Map of What You Can Do

Inclined starts with a skill realm — a shared set of skills organized by domain, configured for your workspace. You rate each skill on two simple scales: how proficient you are, and how interested you are in growing there. You can attach notes and evidence links to any skill, so your assessment carries its reasoning with it.
Three small steps. One unmistakable picture.

#### Terrain, not tables

Every skill in your realm is a tile; proficiency lifts it into the landscape. Comfortable areas spread into grassland, mastery rises to a snowy summit, and skills you've never assessed stay under fog. Select any region of the map and a detail panel shows the skill's rubric, your rating, your notes, and your evidence.

#### Cliffs, plateaus, and strengths

Inclined reads your terrain the way a hiker reads a map. Steep drops between adjacent skills surface as cliffs — places where deep expertise sits next to a gap. Flat, comfortable regions with no active growth show as plateaus. Neither is a judgment; both are worth knowing about.

#### Growth focus

Flag the one to three skills you're deliberately climbing this season. They get a beacon on the map, so a quarter's intent is legible at a glance — to you, and to anyone you choose to share your terrain with.

#### Time travel

Every change to your assessment is recorded automatically, with no extra effort from you. Rewind your terrain to any past moment, drop a named snapshot at milestones ("End of Q1," "Before the AI training"), compare any two points to see exactly what moved, or press play and watch your whole landscape grow. It is the natural artifact for a 1:1 or a quarterly review — where you came from, not just where you stand.

#### Made for teams, careful with visibility

Realms are shared per workspace, with admin tools for managing members and the skill realm itself. Visibility is yours to set: keep maps to admins, or let members see each other's terrain. Your assessment is always yours alone to edit.

### Designed to Stay Out of Your Way

Inclined follows the same principle as the rest of the En Dash toolkit: better systems do not always need to be bigger systems. There are no performance scores, no rankings, no manager overrides of your self-assessment. The map reflects what you say about yourself — Inclined just makes it visible, and keeps the history so growth becomes something you can watch rather than something you have to remember.

### Who It's For

Inclined is for individuals who want an honest picture of their own capability, and for small teams who want skill conversations grounded in something better than memory. It is especially at home in quarterly planning, growth conversations, and onboarding — anywhere "where are we strong, and where are we climbing?" is the real question.

---

# Learn AgentCore

- **Type**: App
- **URL**: https://endash.us/toolkit/items/learn-agentcore
- **Tags**: ai, development, guide


### What is Learn AgentCore?

Learn AgentCore is an interactive course for Amazon Bedrock AgentCore. Not a model. Not LangGraph. A platform for running agents in production: isolation, identity, tools, policy, memory that outlives a process.
You step a live session in the browser and watch the jobs after the loop works: Tuesday traffic, two customers on one host, Slack as Maya, a $500 rule. The goal is to get someone from "I have a graph on localhost" to "I can see what has to sit around that graph."

### Why We Built It

AgentCore is easy to name and hard to place. The docs will give you Runtime, Gateway, Identity, Policy, Memory, Observability. The thing that actually matters is the job after the loop works.
LangGraph is the loop. AgentCore is how that loop runs when two customers share a host, when an IdP has to say who may call, when the company API should be wrapped once, when $500 is a rule, when terse replies must still be true next month, or when you need to find a denied refund in a trace.
We built Learn AgentCore so people can step that factory floor instead of only reading the product names.

### A Hands-On Way to See the Session

This is not a slide deck about AWS.
You pick a module, press Step, and watch a session live: a microVM, inbound identity, outbound OAuth, Gateway MCP, Cedar policy, short-term and long-term memory, traces. No AWS key. Quizzes stay in this browser. Sign in with your En Dash account if you want progress and places on another machine.

### Built Around Jobs, Then the Platform

Two doors.
Use cases are the jobs: Tuesday traffic, two customers, Slack as Maya, a $500 spend cap, memory that outlives the process, a denied refund you can find. Each one is "what localhost does" versus "what the platform does," then a link into the matching module.
Learn is twelve modules on the AgentCore platform itself: Runtime sessions, Harness, Gateway, Identity, Policy, Memory, Observability. The capstone puts them in one session.

### Useful for Engineers Who Already Have a Loop

This is for people whose graph works on one laptop with a dotenv, and who now have a second customer.
Production isolation. An IdP. MCP wrap. Deterministic policy. Durable memory. Traces. If the agent still lives on localhost, skip it. Learn AgentCore is for the other case.

### Built to Make the Idea Click

Some product ideas fit in one sentence. AgentCore needs a session you can watch.
Learn AgentCore exists so more people can see what the platform is for, when a laptop is cheaper, and what it looks like when an agent actually leaves.
Not official AWS. A community resource from En Dash, same shop as Learn LangGraph, html-in-canvas.dev, and learn-pretext.com.

---

# Learn LangChain

- **Type**: App
- **URL**: https://endash.us/toolkit/items/learn-langchain
- **Tags**: ai, development, guide


### What is Learn LangChain?

Learn LangChain is a comparative studio for the LangChain stack. Same Tuesday ticket, four runtimes: a chain, create_agent, create_deep_agent, and a LangGraph.
You pick a job and a runtime and run it. A chain searches once. A loop can search again. A harness brings a filesystem you may not need. A graph can wait for a person. The goal is to get someone from "I have heard of LangChain" to "I can pick a shape for this ticket."

### Why We Built It

LangChain is a pile of product names. Chain, LangChain, Deep Agents, LangGraph, LangSmith, Agent Server, Fleet, Engine, LLM Gateway. The docs will give you all of them. The thing that actually matters is the job: which runtime for this Tuesday ticket.
A PDF one-pager is a chain. Docs that have to look again are a loop. A rental that waits for a person is a graph. A QBR that needs files and subagents is a harness. A morning digest that a human should see before it sends is a harness plus a pause.
We built Learn LangChain so people can run those jobs instead of only reading the catalog.

### A Hands-On Way to Compare Four Runtimes

This is not a slide deck about the stack.
You pick a job, pick a runtime, press Play. The matrix is five tickets by four machines. After the run, a Smith drawer shows a simulated trace, eval, deploy, and gateway. No API key. Nothing calls a model. Sign in with your En Dash account if you want progress and places on another machine.

### Built Around Jobs, Then the Stack

Two doors.
Jobs are the tickets: PDF one-pager, grounded docs, rental gate, QBR, morning digest. Each one has a runtime that fits and one that does not.
Studio is the matrix. Same ticket as a chain, a loop, a harness, and a graph. The glossary on the landing is what the words mean here, not a product brochure.

### Useful for Engineers Choosing a Shape

This is for people who already ship LLM features and are staring at four product pages.
If the steps are known and the work never comes back, stay on a chain. If the model needs to try again, use create_agent. If the job is long and messy enough to need files and subagents, use Deep Agents. If you need a custom mix of code, one LLM, and a human pause, draw a graph. Learn LangChain is the place to see those four next to each other.

### Built to Make the Idea Click

Some product ideas fit in one sentence. This stack needs the same job, four times.
Learn LangChain exists so more people can see which runtime fits, which one is overkill, and which one cannot do the job at all.
Not official LangChain. A community resource from En Dash, same shop as Learn LangGraph, Learn AgentCore, html-in-canvas.dev, and learn-pretext.com.

---

# Learn LangGraph

- **Type**: App
- **URL**: https://endash.us/toolkit/items/learn-langgraph
- **Tags**: ai, development, guide


### What is Learn LangGraph?

Learn LangGraph is an interactive course for LangGraph — the runtime for agents that need to loop, branch, remember, and pause. Not a new model. A graph over shared state.
You step a live graph in the browser and watch the jobs a chain cannot do: a ticket that looks again, a refund that waits, a researcher that isn’t done. The goal is to get someone from “I have heard of LangGraph” to “I can see what it is for, and I know when to leave the chain alone.”

### Why We Built It

LangGraph is easy to name and hard to feel. The docs will give you nodes, edges, checkpointers, and interrupts. The thing that actually matters is the job: work that has to come back.
A list can only go forward. Support retries. Research re-queries. Refunds sit for a human. Twelve tickets become one standup brief. A flaky test gets edited until it passes. The user comes back on Tuesday. The moment you need a cycle, a pause, or a fan-out, you are already drawing a graph.
We built Learn LangGraph so people can step those jobs instead of only reading the vocabulary.

### A Hands-On Way to See Why a List Dies

This is not a slide deck about agents.
You pick a module, press Step, and watch the token move. Lookup misses, the graph loops, state accumulates, an interrupt holds the run, a fan-out joins. No API key. Quizzes stay in this browser. Sign in with your En Dash account if you want progress and places on another machine.

### Built Around Jobs, Then the Runtime

Two doors.
Use cases are the jobs: a ticket that looks again, a refund that waits, a question that isn’t done, twelve tickets for standup, tests until they pass, the same thread on Tuesday. Each one is “what a chain does” versus “what a graph does,” then a link into the matching module.
Learn is twelve modules on the LangGraph runtime itself: state and reducers, routing, ReAct cycles, checkpointers, interrupts, Send and Command, subgraphs, Store versus checkpointer, multi-agent. The capstone puts them in one graph.

### Useful for Engineers Choosing a Shape

This is for people who already ship LLM features and are staring at a chain that keeps growing a special case.
Support and HITL. Research that has to re-query. Map-reduce over a pile of items. A coding agent that is just a loop. A run that has to survive until Thursday. If the path is A then B then C and it never comes back, stay on a chain. Learn LangGraph is for the other case.

### Built to Make the Idea Click

Some product ideas fit in one sentence. LangGraph needs a loop you can watch.
Learn LangGraph exists so more people can see what the runtime is for, when a list is cheaper, and what it looks like when the work actually comes back.
Not official LangChain. A community resource from En Dash, same shop as html-in-canvas.dev and learn-pretext.com.

---

# Learn Pretext

- **Type**: App
- **URL**: https://endash.us/toolkit/items/learn-pretext
- **Tags**: development, ux, ui, guide, continuousimprovement, product


### What is Learn Pretext?

Learn Pretext is an interactive learning app for exploring Pretext, the JavaScript text measurement and layout library created by Cheng Lou.
It is designed to make a technical library easier to understand through hands-on demos, tutorials, and visual experimentation. Instead of only reading API docs, learners can see how Pretext behaves, test ideas directly, and build intuition for what becomes possible when text layout is computed arithmetically rather than through repeated DOM measurement. Learn Pretext describes itself as “interactive demos and tutorials for @chenglou/pretext” and frames the experience around “text layout at the speed of arithmetic.”

### Why We Built It

Pretext is a powerful idea, but it opens up a part of UI engineering that many developers have never had a chance to explore deeply.
The library is built for fast, accurate multiline text measurement and layout in JavaScript and TypeScript, with support for DOM, Canvas, SVG, and more. It avoids DOM measurement calls like getBoundingClientRect() and offsetHeight, which can trigger expensive layout reflow in the browser. That makes it interesting not just as a library, but as a new mental model for building text-heavy interfaces. Learn Pretext exists to help people cross that gap from “this sounds impressive” to “I understand how to use this.”

### A Hands-On Way to Learn a New UI Primitive

Learn Pretext turns a technical concept into something you can actually play with.
The app uses interactive examples and guided exploration to help people understand what Pretext does well, where it differs from traditional browser layout approaches, and what kinds of interfaces it unlocks. That includes the core problem Pretext addresses: measuring and laying out wrapped text without depending on browser reflow in the hot path.

### Built Around Demos, Tutorials, and Exploration

Learn Pretext is not just a reference site. It is a learning environment.
It is built for developers who want to understand both the mechanics and the possibilities of Pretext through direct interaction. By combining tutorials with runnable demos, it helps people move from passive reading into experimentation, which is especially useful for a topic as visual and behavior-driven as text layout. The site positions itself explicitly around interactive demos and tutorials, which makes that learning approach central to the product rather than secondary to documentation.

### Useful for Developers, Designers, and UI Tinkerers

Learn Pretext is especially relevant for people building interfaces where text layout matters a lot.
That includes chat interfaces, editorial layouts, tight multiline UI, canvas-based interfaces, custom rendering systems, and other experiences where text geometry affects interaction and presentation. Pretext’s broader value comes from making text measurement dramatically faster and more flexible than traditional DOM-based approaches, and Learn Pretext helps people understand those possibilities in a concrete way.

### Built to Make a New Idea Click

Some tools are best learned by reading. Others make more sense once you can see and manipulate them.
Learn Pretext is built around that second kind of learning experience. Its goal is to make an advanced layout concept feel approachable, visual, and practical — helping more people understand what Pretext is, why it matters, and how to start thinking with it.

---

# Learn vgpu

- **Type**: App
- **URL**: https://endash.us/toolkit/items/learn-vgpu
- **Tags**: development, ui, ux, guide, tooling


### What is Learn vgpu?

Learn vgpu is an interactive studio for vgpu, Vercel Labs’ tiny TypeScript WebGPU API. Five calls. One value per step. Then Run.
You edit vec4f() on step 1 and watch the canvas change. Then you walk init, effect, frame, target, and html. Same program in the browser, on Dawn (vgpu/node), and in CI (vgpu/mock). The goal is to get someone from “I have heard of WebGPU” to “I can write one file that is a live canvas, an OG PNG, and a pixel snapshot.”

### Why We Built It

WebGPU is easy to name and hard to start. Most libraries want to be an engine. vgpu wants to be a small function: init, effect, frame, target.
The thing that actually matters is one program with three lives. A tab. A serverless PNG. A CI snapshot. Bindings are WGSL names, not bind-group indexes. Change a value, hit Run.
We built Learn vgpu so people can step those five calls instead of only reading the spec.

### A Hands-On Way to See the Same Program Three Ways

This is not a slide deck about shaders.
You open the studio, change the four numbers in vec4f, press Run, and the canvas updates. Later steps name one value: tint, the sin frequency, the offscreen vec4, or the HTML warp. No login. No API key. Sign in with your En Dash account if you want progress on another machine.

### Built Around Five Calls, Then Three Runtimes

Two doors.
The studio is the lesson: init (one handle), effect (bindings are names), frame (explicit passes), target (readback / OG), html (HTML-in-Canvas extra credit). Each step asks you to change one value.
Runtimes are the same file: browser canvas, vgpu/node (Dawn, no window), vgpu/mock (CI, no GPU). The holographic foil on html-in-canvas.dev is extra credit, not this lesson.

### Useful for Engineers Who Need GPU Work Outside the Tab

This is for people who already ship web graphics and are staring at a WebGPU sample that only lives in a window.
OG images. Pixel diffs. Headless CI. If the shader only has to paint a canvas, a demo is enough. Learn vgpu is for the other case: the same WGSL as a live canvas, a serverless PNG, and a snapshot.

### Built to Make the Idea Click

Some product ideas fit in one sentence. vgpu needs a color you can change.
Learn vgpu exists so more people can see what the tiny API is for, when an engine is overkill, and what it looks like when one program leaves the tab.
Not official Vercel. A community resource from En Dash, same shop as Learn LangGraph, Learn LangChain, Learn AgentCore, html-in-canvas.dev, and learn-pretext.com.

---

# MIT Beer Game

- **Type**: App
- **URL**: https://endash.us/toolkit/items/beer-game-app
- **Tags**: management, workforce, teamwork, leadership, outcomes, dependency, projectmanagement, product


### What is Beer Game?

Beer Game is an interactive supply chain simulation in the En Dash Toolkit that makes the bullwhip effect visible, immediate, and memorable.
Based on the classic MIT Beer Game, it places players inside a four-stage supply chain where each participant makes one simple decision each round: how much to order. What looks straightforward quickly becomes chaotic as delays, incomplete information, and local decision-making amplify small demand changes into major swings in inventory, backlog, and cost. The En Dash implementation brings that lesson into a modern web experience with solo play, sandbox experimentation, and multiplayer hosting for workshops and group sessions.

### Why We Built It

The Beer Game has been teaching systems thinking and supply chain dynamics for decades, but many versions still rely on physical setups, facilitation overhead, or limited visibility into what actually happened during play.
We built Beer Game to make this lesson easier to access and easier to teach. By turning the simulation into a clean digital experience, participants can move quickly from playing the game to understanding the deeper patterns underneath it. That makes it useful not only for classrooms, but also for product teams, operations groups, leaders, and anyone trying to understand how rational local decisions can produce irrational system-wide outcomes.

### A Practical Systems Thinking Simulator

Beer Game turns an abstract concept into a direct experience.
Players take the role of retailer, wholesaler, distributor, or factory inside a delayed supply chain. Each week, they react to incoming orders and shipments while managing inventory, backlog, and cost. Because no one has full system visibility during play, even small changes in customer demand can create dramatic instability upstream. The result is a hands-on demonstration of how structure, delay, and fragmented information shape behavior.

### Built for Learning, Experimentation, and Facilitation

Beer Game is designed for low friction and flexible use.
It supports:
- Solo mode for quick individual learning
- Sandbox mode for experimenting with scenarios and exploring system behavior more freely
- Multiplayer / host / workshop mode for live group play, facilitated sessions, and team learning
That range makes it useful for self-guided exploration, classroom instruction, team workshops, and leadership discussions about systems behavior.

### See the Bullwhip in Your Own Data

The lesson does not end when the game is over.
Beer Game includes replay and analytics views that show how decisions unfolded across the full simulation. Players can review order amplification, inventory and backlog patterns, cost breakdowns, and week-by-week progression across the chain. Instead of only hearing about the bullwhip effect, participants can see exactly how it emerged from their own decisions.

### Built for Clarity, Not Complexity

Beer Game is designed to keep the focus on the learning experience rather than the interface.
The application presents the core mechanics clearly, emphasizes the current role and decision, and makes the consequences legible through visual replay and analytics. It stays faithful to the classic MIT rules while making the experience faster to start, easier to facilitate, and more useful in modern teaching and team settings.

---

# n-Digest

- **Type**: App
- **URL**: https://endash.us/toolkit/items/n-digest
- **Tags**: focus, communication, growth, product, development, guide


#### What is n-Digest?

n-Digest is a lightweight web app in the Endash Toolkit designed to help people capture, revisit, and work with ideas from books that matter to them.
It’s especially helpful for people who consume books through audiobooks, where insights can be powerful in the moment but difficult to retain over time. n-Digest helps turn those fleeting insights into something more durable and useful.

---


#### Why We Built It

Many of us at En Dash listen to far more books than we read. Audiobooks make learning accessible during commutes, walks, or everyday routines—but they also make it easy for great ideas to fade once the book ends.
We built n-Digest to help bridge that gap. The goal was to create a simple way to revisit key concepts, explore how ideas connect, and maintain a working relationship with books long after finishing them.

---


#### Making Books More Digest-able

Books often contain a spine of core ideas supported by a web of related concepts. n-Digest helps surface those structures so they can be revisited, explored, and reflected on.
Instead of treating a book as something you finish and move on from, n-Digest encourages a more active relationship—returning to important ideas and deepening understanding over time.

---


#### A Companion for Reflective Learners

n-Digest is designed for people who enjoy thinking deeply about what they read (or listen to). It supports practices like revisiting key concepts, exploring interpretations, and connecting ideas across different books.
At En Dash, we use it both for our own learning and for sharing insights internally and with our broader community.

---


#### An Experiment in Better Thinking

n-Digest is also one of the ways we’re experimenting with AI-assisted thinking tools at En Dash. Rather than focusing on speed or automation, the goal is to support reflection, synthesis, and deeper understanding.
Like the other tools in the Endash Toolkit, it started with a simple question: how can we make learning from great books a little more durable—and a little more useful?

---

# n-dx

- **Type**: App
- **URL**: https://endash.us/toolkit/items/n-dx
- **Tags**: development, workforce, ai, focus, product, prompts


### What is n-dx?

n-dx is a CLI toolkit in the En Dash Toolkit that connects codebase analysis, structured planning, and AI-driven task execution into a single repeatable development loop.
Instead of treating AI coding as isolated prompts or file edits, n-dx operates at the project level. It analyzes the structure of a codebase, generates a structured product specification, and then executes tasks against that spec—keeping development organized, traceable, and repeatable.

### Why We Built It

Most AI development tools generate code quickly, but they don’t maintain a clear understanding of the project they’re working on. Without a shared source of truth, each session starts from scratch and codebases accumulate technical debt faster than teams can manage it.
We built n-dx to introduce structure into AI-assisted development. By maintaining a living product specification derived from the codebase itself, teams can keep planning, implementation, and system understanding aligned.

### A Closed Development Loop

n-dx organizes development into a continuous loop:
1. Analyze – map the codebase structure and architecture
1. Plan – generate and maintain a structured PRD with epics and tasks
1. Execute – autonomously implement tasks and update progress
Each cycle begins with understanding the current codebase and ends with shipped work, with the PRD acting as the persistent source of truth throughout the process.

### Built for Real Codebases

n-dx is designed for teams working on existing systems, not just prototypes.
It helps developers:
- understand unfamiliar repositories quickly
- bring structure to fast-moving or “vibe-coded” projects
- maintain a living plan alongside the code
- keep AI development sessions connected through persistent state
The result is faster iteration without sacrificing maintainability or architectural clarity.

### A Practical CLI Tool

n-dx is CLI-first and fits directly into existing development workflows. Developers can point it at a repository and start the loop with just a few commands.
The system works with multiple LLM providers and keeps its project state directly in version control, making progress visible and traceable without introducing new planning tools or complex infrastructure.

---

# n-URL

- **Type**: App
- **URL**: https://endash.us/toolkit/items/n-url-app
- **Tags**: remote, communication, teamwork, collaboration, smallbusiness, product


#### What is n-url?

n-url is a lightweight URL shortener and QR code generator built by En Dash as part of the Endash Toolkit. It provides simple, reliable short links while automatically generating QR codes for any shortened URL. Users can also generate QR codes for any URL directly, even without shortening it.
The tool focuses on practical, everyday needs—sharing links in presentations, documents, signage, and internal communication—without the friction or uncertainty that often comes with third-party link shorteners.

---


#### Why We Built It


---


#### Reliable Links for Real Work

Because n-url is part of the Endash ecosystem, links created through it are intended to remain stable and dependable. We built it for ourselves first—so that links used in presentations, documentation, and long-lived materials would continue working over time.
This reliability matters whenever a link appears in places that can’t easily be updated later: slides, printed materials, QR codes, or documentation shared with partners and clients.

---


#### QR Codes by Default

Every shortened link created in n-url automatically comes with a QR code. This makes it easy to move between physical and digital contexts—whether sharing a link in a meeting room, on a poster, in documentation, or during a talk.
You can also generate a QR code for any existing URL without creating a shortened link, keeping the tool flexible for different use cases.

---


#### Built for Teams

n-url includes team workspaces, allowing multiple people to manage links within a shared environment. This makes it easy for teams to organize, reuse, and maintain the links they rely on for presentations, internal documentation, and collaborative work.
Instead of individuals creating links scattered across different services, teams can manage them together in one place.

---


#### A Simple Tool That Solves a Real Problem

Like many things in the Endash Toolkit, n-url exists because we needed it ourselves. It’s intentionally simple: shorten links, generate QR codes, and ensure they keep working.
Sometimes the best tools come from solving one painful moment—and making sure it never happens again.

---

# Prodeo

- **Type**: App
- **URL**: https://endash.us/toolkit/items/prodeo-app
- **Tags**: focus, async, remote, communication, teamwork, collaboration, ui, ux, product


#### What is Prodeo?

Prodeo is a simple screen-capture video tool built by En Dash as part of the En Dash Toolkit. It allows people to quickly record and share short videos that demonstrate ideas, workflows, products, or features.
The goal is straightforward: make it extremely easy to show something instead of explaining it in text.

---


#### Why We Built It

At En Dash, we often needed to share short screen recordings with teammates and with the broader community. The existing tools we tried either required too much setup, complex editing workflows, or specialized knowledge of video software.
Rather than asking everyone to learn tools like After Effects or other professional editing software, we decided to build something much simpler. Prodeo focuses on quick capture, quick sharing, and clear communication.

---


#### Show, Don’t Explain

Many ideas are easier to demonstrate than describe. Prodeo makes it easy to record your screen, walk through a workflow, or highlight a product feature in a short video.
Instead of writing long explanations or scheduling a meeting, a quick recording can often communicate the idea faster and more clearly.

---


#### Built for Learning and Communication

We use Prodeo across En Dash for both internal and external training, helping teammates and partners quickly understand tools, workflows, and product capabilities.
It’s also frequently used to create product videos, showing how a product works or highlighting new features in a clear and practical way.

---


#### A Tool We Built for Ourselves

Like many tools in the En Dash Toolkit, Prodeo started as an internal need. We wanted a fast, simple way to capture and share knowledge without requiring specialized software or video production skills.
So we built it—and it quickly became part of how we teach, explain, and demonstrate ideas.

---

# SpaceTrader

- **Type**: App
- **URL**: https://endash.us/toolkit/items/spacetrader-app
- **Tags**: ai, development, game, fun

Most remakes of old games modernize away the thing you loved. Space Trader keeps it: the same buy-low-sell-high hustle, the same pirates on your tail, the same little galaxy that once lived on a Palm Pilot — now living in a single web page. Dock, trade, jump, survive, and retire rich enough for the moon.

### Why We Built It

Twenty-some years ago this game lived in a shirt pocket, played in stylus-sized sessions while standing in line. We missed it — not a museum copy of it, but the feel of it: quick decisions, real risk, a run that ends with a score worth bragging about. So we rebuilt it faithfully for the web, and used the project as a proving ground for how we build now — the entire thing planned, executed, and reviewed by the newest AI models working through n-dx, our own agent toolkit. One half nostalgia, one half laboratory. Both halves shipped.

### A Galaxy That Fits in One File

You start as a new commander with a small ship, a thousand credits, and a debt-free future nobody expects you to keep. A hundred and twenty solar systems sit within jump range of ambition: each with its own government, tech level, and prices that move with events. Buy water where it's cheap, sell firearms where it's legal, and decide how much cargo you're willing to lose to the next pirate who doesn't like your answer.
Trade. Jump. Repeat. Retire before the galaxy collects.

#### Buy low, sell high, stay sharp

Ten goods, live price events, and markets shaped by politics — a war zone pays for firearms, a plague pays for medicine, and a boring agricultural backwater pays for almost nothing. The trading game rewards attention, not grinding: every route you discover is one the galaxy was already hinting at.

#### Encounters at every jump

Pirates want your cargo, police want to inspect it, and traders occasionally want to make you an offer mid-flight. Fight, flee, bribe, or surrender — your reputation follows you either way. When a fight goes truly wrong, an escape pod is the difference between a setback and a headstone.

#### Wormholes and strange days

Three wormhole pairs offer instant passage across the map for a toll, bending every route calculation around them. And the galaxy has moods: special events and quest chains surface as you play, the same way they did on the original — quietly, and usually at the worst possible time.

#### Five difficulties, one scoreboard

From Beginner to Impossible, the game scales the danger, not the rules. Every run ends in a score built from net worth, days survived, difficulty, and kills — and a decision about when you're wealthy enough to stop pushing your luck.

#### Yours anywhere, signed in or not

The whole game ships as one self-contained HTML file: it plays in any browser, saves locally, and works with no connection at all. Sign in with your En Dash account and your progress is ready for cloud saves and an En Dash-wide retirement leaderboard — but signing in is always optional. The game never puts the fun behind a login.

### Faithful by Design

Space Trader follows the same principle as the rest of the En Dash toolkit: better systems do not always need to be bigger systems. There are no microtransactions, no energy timers, no engagement mechanics the original never had — and no framework underneath, either. The game is dependency-free vanilla JavaScript in a single file, its interface a first-class recreation of the Palm OS original, and every build has to survive a gauntlet of automated balance and invariant checks that play thousands of trips headlessly before a human ever loads the page.

### Who It's For

Space Trader is for anyone who remembers a gray plastic rectangle fondly, and for anyone who never met one but likes strategy in five-minute sips. It's at home in a browser tab between meetings, on a phone in a waiting room, and anywhere "one more jump" is the real question. And if you're curious what it looks like when AI agents build and operate a real product end to end — this is one, and it's live at spacetrader.endash.us.

---

# AI for SMBs: Why Generative AI Matters for Small Businesses

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/Why-GenAI-Matters-for-SMBs
- **Tags**: ai, smallbusiness

> This article is part of the “AI for Small Business” series: a practical guide to using generative AI to save time, reduce costs, and improve how you work. Each post explores real tools, platforms, and frameworks that small business owners can use to improve writing, operations, and customer service. The series will also include a live webinar where participants can see these tools in action, follow goal-based workflows, and ask questions about applying AI in their own business.
Running a small business often involves juggling multiple responsibilities at once. Owners handle emails after hours, try to keep social media up to date, and squeeze in bookkeeping late at night. Time is scarce, budgets are constrained, and customer expectations continue to rise.
Generative AI is arriving at a critical moment. Tools that once required enterprise-level budgets are now available as browser apps or affordable subscriptions. They provide faster workflows, clearer insights, and easier ways to reach customers. For small businesses, the value is immediate: saving hours, avoiding costs, and improving service without hiring additional staff.
The question is no longer whether AI works. It does. The challenge is identifying which tools deliver real value in the context of everyday operations, and how to deploy them responsibly.

### The AI Landscape

Generative AI tools align closely with small business needs:
- Writing & Reasoning: Drafting emails, summarizing meetings, writing proposals.
- Automation Platforms: Linking apps and streamlining workflows.
- Agents & Orchestration: Tools that act autonomously across multiple steps.
- Analytics & Decision Support: Turning raw data into forecasts and insights.
- Customer Experience: Chatbots and assistants that engage customers.
- Design & Content Creation: Affordable production of visuals, videos, and graphics.
- Audio & Voice: Transcription, editing, and natural voiceovers.
- Industry-Specific Solutions: Tailored platforms for fields like retail, hospitality, or real estate.
Each plays a distinct role. Together, they address time, cost, and customer service simultaneously.

### Why It Matters Now

Small businesses are already seeing clear results from using AI.
- Retail – Shop owners use ChatGPT to create product listings in minutes instead of hours. 
- Consulting – Proposal prep time drops by as much as 75% with AI-assisted templates.
- Restaurants – Canva AI helps design menus and promotions without hiring agencies.
- Grocers – Forecasting tools cut food waste and improve margins.
These examples show how AI meets the daily pressures of running a small business—less time spent on routine work, lower costs, and faster service.
At the same time, broader trends make this the right moment to adopt AI.
- Rapid SMB adoption – Owners are embedding AI into daily workflows to save time and money. Teams are offloading repetitive tasks to focus on service, creativity, and customers who now expect quicker, smarter experiences without higher prices.
- Market growth & investment – Approximately 98% of US companies have one hundred or fewer employees. Analysts project AI spending by SMBs to grow about 25–30% annually through 2030. AI skills are also becoming a standard part of business literacy, shaping how companies hire, market, plan and operate.
- Efficiency, risk, and opportunity – AI reduces administrative errors, speeds up decisions, and gives leaders better data for managing operations. Responsible use (verifying outputs and protecting customer privacy) will separate trusted businesses from careless ones. Early adopters in local communities are gaining competitive advantages and stronger customer loyalty.
Put simply, AI is moving from optional to expected. The businesses that learn to use it now will stay efficient, credible, and competitive in the years ahead.  

### Bottom line

Small businesses need time back. Generative AI helps by taking on routine work including writing, summarizing, basic analysis, and everyday communication. Start with one task and see what changes. Measure the results. If it saves time or improves service, build from there.
AI doesn’t replace human judgment; it supports it. The goal is to make work easier, faster, and more focused on customers. For most small businesses, that’s the smartest place to start.
> This article kicks off the “AI for Small Business” series. Upcoming posts and our companion webinar will walk through the key AI tools and workflows that help small businesses manage writing, automation, analytics, customer experience, and creative design. 
> The webinar will feature real examples, step-by-step demonstrations, and a chance to explore how to apply AI directly to your business goals. 
Register for the event here: https://www.linkedin.com/events/gettingstartedwithgenaiforsmall7383559419814612992/
If you’re interested in getting started today, please also check out our numerous GenAI Prompting “Field Guides” in our toolkit here: https://endash.us/toolkit 

---

# Asynchronous Chats

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/asynchronous-chats
- **Tags**: communication, remote, async, culture, teamwork

Picture this…you are heads down, in a groove, cranking out your to do list. Tss Tss Tss: Slack ping. Microsoft Chime: Teams Message. Enter the distraction. While we may be working in an increasingly remote world, we are still somehow facing the same amount(if not more) of distractions that we face in the office. While many of these distractions are just a matter of course of how we do business, one of the major contributors to interrupted work and therefore incredibly expensive context switching are the chat or messaging tools. 
Our working relationship with these tools is complex. On the one hand, we rely on them for communication, collaboration, problem solving etc etc etc. That being said, they are also incredibly intrusive interruptions to any “rhythm” we may be striving to achieve at work. So how do we solve this paradox? Here are some concrete ways to leverage these messaging tools with guardrails so that they don’t act as a constant barrier to flow state and productivity. 

### Saying “I’m Not Available”

- Use the “away” feature available in Slack.
- Set standard Heads Down time for the whole team. During this time, all team members refrain from sending messages to one another.
- Assign one team member to manage any channels that are externally facing each week, this way only one person at a time has to deal with the “noise” of messages.
- Customize notification settings to control how often you're alerted about new messages. Use "Do Not Disturb" mode when you need focused work time.

### Organizing Content

- Create dedicated channels with specific purposes to allow for selective notifications depending on the topic.
- Within each channel, use threads to keep conversations organized 
- Use reaction emojis to quickly acknowledge messages without needing to write a response.
- Use formatting tools like bullet points, lists, and headings to make your messages more organized and easily scannable. 

### Communicating with “Heads Down” Colleagues

- Schedule messages to send at a later point in time.
- Encourage respect for response times.
- Implement guidelines for how to indicate the urgency of a communication.
- Share documents or files with plenty of time built in for feedback and collaboration

---

# Asynchronous Stand Ups… and Sit Downs

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/async-stand-ups-sit-downs
- **Tags**: async, collaboration, teamwork, communication

As the world of software development continues to wander down the remote work path, it can make one wonder…what else can we shake up? There are so many aspects of a daily office life that could use a revisit: a new lens, a new perspective a new approach…a new way. One of those aspects is meetings. We can all probably think about a job where meeting culture was the status quo. That being said, status quos are meant to be scrutinized periodically…let’s schedule a meeting to talk about it. 

### Let’s Pull Up

Meeting culture has some great positives. There are fairly obvious benefits to the “getting everyone in the room (or zoom)” approach to work and problem solving. Those real time decisions are impactful and can help to launch a project into a new phase or clear a roadblock or create some amazing artifacts. When a slack thread hits 40 messages, some of us are inclined to say. Enough! Let’s pull up and discuss. Sometimes, that may be the right move, sometimes it may just be introducing an unnecessary roadblock to momentum. If everyone on that thread is immediately free to discuss the issue, then great! Take those 10 minutes, hash it out on a zoom call then hang up and go forth and prosper. Just make sure you document the outcome of that call in that slack thread. 
What happens if only two of those people is free to hop on a zoom call? Or if someone in the chat hasn’t weighed in yet because they are deep in a coding flow and have *gasp* silenced their Slack notifications. The thread AND the meeting missed that person. Rather than giving that asynchronous problem solving time to play out, our natural inclination towards meeting culture rushed the conclusion. In some cases, the conclusion of the meeting may have been exactly the right thing…but at what cost? 

### A Shift To Async

There is an increasing focus on researching and quantifying the cost of context switching. I won’t attempt to offer that calculation here, but rather make the point that a meeting is the ultimate context switch. Every time you have to stop what you are working on to walk down the hall to a conference room or join a zoom call, you lose a little part of the day. It takes time to draw out of what you are doing and dive back into it the next time. A day full of meetings usually equals the same thing for folks - mental fatigue and a lack of productivity. 
Very little of what we do is intensely time sensitive in software development. Sometimes there is a crucial bug that we have to jump on and solve immediately (especially when our work is customer facing and our bugs customer impacting), but a lot of times questions posed can be answered at a later time. Everything does not need to be discussed real time in a collaborative setting.

### The Power of Tools with Norms

How do we solve it…tools! Tools alone cannot solve this problem. There are some excellent tools on the market to empower companies to even just take a step away from meeting culture towards asynchronous work. That being said, more software is not the answer in and of itself. We have all been in situations where the chat tool of the day ends up creating stress, discord and distraction throughout (and sometimes well beyond) our work day. When tools are implemented as a “band-aid” rather then as part of a thoughtful solution to the root issues around collaboration within a team they run rampant and often exacerbate the underlying problems rather than solve them. 
When we make a decision to adopt a new tool, thinking through how we want our teams (and how people ultimately will) to use it is an important step. Training on a new tool is fairly intuitive; tailored training for specific teams around tool norms is a bigger leap. 

#### Who should establish the norms? 

Sometimes it can be difficult for enterprise-wide norms around a tool to be delivered in a top down, ubiquitous fashion. This can be for many reasons. Perhaps leadership is a little too disconnected from the day-to-day behaviors of employees or teams across the organization. It could also be that the tool is too unfamiliar to anticipate the exhaustive list of norms that may be needed as it is adopted across the organization. While these issues can be daunting as we “shop” for new tools to support our asynchronous collaboration goals, it is important to have some guardrails in place before rolling out access. 
Enterprise norms can come from all different places within the organization. Here are some options: 
- The executive leadership team
- A culture committee (or whatever name it has in your place of work)
- Crowdsourcing 
Another approach is to keep the enterprise norms somewhat high level and provide time and space for teams to generate their own norms. These can be posted or shared in a public forum in case one team’s norms resonate with another…we can borrow from each other this way. 

#### Revisit and Revise…Often

As with any norms, they can get stale. Team members come and go, tools release new functionality, we shift how we work, or we learn new things about a tool: all of which may call for a norm revisit. This can take many forms depending on the level (team based or enterprise wide) of your norms and the size of your organization. Regardless of what it may look like where you work, the practice of reflecting on why we do things the way we do them is a powerful one and it can be an important key to effectively leveraging tools that support asynchronous collaboration. 

### Some Tool Norms to Get Started

This list is in no way exhaustive, but it is a nice launch pad from which to jump into the world of asynchronous engagement models within a project team, office group or at an enterprise wide level.
- Create rules for chat tools as they relate to work. This can take a few different forms such as:
- Assign topics or types of communication to different mediums. For example: 
- Leverage the use of away messages or statuses for team members to communicate time in deep focus or flow state and silence app notifications 
- Establish company wide (or department or team wide) focus times 

### Not all Meetings are Created the Same

While there are many merits in guarding against meeting culture, there is still a place for meetings in our workplaces. It is difficult for most teams and organizations to conceptualize a world without any real time collaboration. While it may be possible in some instances, there is something to be said for operating within our comfort zones. 
Thinking about why we are meeting or why we think we need to meet before we throw a meeting invite into someone’s planned day is a valuable practice. An eye towards efficiency and a shift towards asynchronous work and collaboration can actually make those real time meetings incredibly more impactful and efficient. If we start to think of meetings as one of many weapons we have in our collaboration arsenal, we can begin to break away from the meeting culture mindset and drastically shift our workday experience. 

---

# Creativity Unboxed: Finding Innovation Within Boundaries

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/creativity-unboxed-finding-innovation
- **Tags**: career, culture, growth, communication, focus, conflict

From birth, through education, and into our careers, boundaries are set in our lives—sometimes self-imposed but often defined by others. Boundaries, rules, constraints, and guidance are different ways of telling us to “stay in our lane” and keep within the scope of our work. While these concepts may seem restrictive, I’ve found that they can actually be a catalyst for creativity. How can we use these limits as a springboard for innovation?

## But First, What is Creativity?

Creativity is not just about sketching a portrait or knitting a sweater. It’s about stretching your mind. Like any skill, it requires practice. Throughout my career, I’ve often heard that constraints stifle creativity. However, I believe the opposite can be true. Let’s focus on creativity in the workplace and how we can harness constraints to drive innovation.

---


## Unlocking Creativity in Your Work

No matter how clearly defined a project may seem, there's always room for creativity. Deliverables often allow for flexibility, even if there’s a specific end goal. For me, working within these boundaries has been a powerful motivator to think creatively and deliver innovative solutions. In fact, constraints have pushed me to learn, grow, and refine my approach.
I encourage you to embrace the limits set for you. Instead of seeing them as obstacles, think of them as frameworks that challenge you to find creative solutions. By doing this, you can exceed expectations and deliver value in ways you hadn’t imagined.

### Be Curious

Curiosity is a driving force for creativity. In my experience, finding areas within your work that offer opportunities for learning, practicing, and innovating can lead to new discoveries.
When faced with a new software or process, explore how others are using it. Watch tutorials, research unconventional use cases, and consider how these tools can solve your problems in ways you hadn’t thought of. Applying new ideas to familiar tasks can lead to improved outcomes and more efficient workflows—all within the boundaries of your role.

### Share your Creativity

Once you start thinking creatively, it becomes contagious! Sharing your creative solutions can inspire others. The challenges you’ve solved are likely not unique to your team—others may be facing the same problems, and your innovations could be a game-changer for them.

#### As a leader

Leaders play a crucial role in fostering creativity. Encourage your team to try new solutions and collaborate on innovative approaches. Providing support and promoting creative thinking can empower your team to push boundaries and achieve greater success. You may even try applying this practice in your own work to lead by example.

#### As a teammate

Proposing new ideas at work can be intimidating, but strong communities of practice and supportive relationships make a huge difference. By building a culture of openness and sharing, everyone can benefit from creative thinking.

### Stretch Your Limits

Within the confinements of your job descriptions, defined deliverables, or working assignments, stretching yourself to your own limits will help to expand on what is being asked of you. Start with questions like “How can I stand out?” “What will make this different?” These questions will spark your imagination and help you bring those ideas to life. 
When beginning a new piece of work, I often analyze the work in a simple way. This may look like an outline or simple powerpoint presentation. Then, I question how this can be displayed to convey the important points or content on the page differently than I have done in the past. This is the perfect opportunity to experiment and challenge your skills in a new way.
Aggressively seeking out different paths than others and even your past self will undoubtedly improve the quality of your work and push you beyond your limits whether it’s expanding on your own work or spreading your wings and putting yourself out there to assist others. This will guide you in the direction of increased learning opportunities and becoming more and more creative over time.

### Break Out of Your Routine

Routine can stifle creativity, so it’s important to break out of it whenever possible. Get out from behind your desk. Take advantage of opportunities like MeetUps, networking events, or even a simple change in environment to spark new ideas.
If you can’t step away from your desk, look for inspiration online. LinkedIn can be a valuable tool for discovering fresh perspectives and learning from others’ experiences. Read blog posts, connect with colleagues, and see how their insights might inspire you.
Sometimes, the best ideas come from unexpected places. That movie you watched or the podcast you listened to might offer a new angle for tackling a work challenge. Just living your life can provide you with experiences that can influence your professional creativity in surprising ways.

---


### Make It Happen

While we all have deadlines to meet and deliverables to complete, the way we approach our work can make all the difference. Although we can’t always change the constraints we’re given, we can control how we navigate them. By drawing inspiration from everyday life, breaking free from routine, and embracing challenges, we can transform the boundaries that once felt limiting into tools for creative growth.

---

# Defining: Modal vs Modeless

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/defining-modal-vs-modeless
- **Tags**: ux, development, ui, design, product

A modal interface takes over: it puts the application into a temporary mode where you must respond—to a dialog, an alert, a login prompt—before you can do anything else. A modeless interface stays out of the way: it remains open and available while you keep working in the main application, like a find-and-replace panel or an inspector. Choosing between the two is one of the most impactful decisions in presenting any task, and this post defines both, with characteristics, examples, and guidance on when each fits.

#### Why are they called "modal" and "modeless"?

The terms modal and modeless derive from the word "mode," referring to a state or condition that alters how an application behaves. A modal interface changes the application's mode by requiring users to interact with it before returning to the main workflow. It places the application into a different state where certain actions are prioritized. Conversely, a modeless interface does not change the application's mode, allowing users to continue interacting with the software without restrictions, thus maintaining a fluid and uninterrupted workflow.

#### Modal vs. model: not the same word

Modal is often confused with model, but they're unrelated terms that happen to sound alike. A model is a representation of something—a data model, a machine-learning model, a business model. Modal is the adjective of mode: it describes an interface state that changes how the application responds to you. If you're comparing interruptive dialogs with non-blocking panels, modal vs. modeless is the comparison you're looking for.

---


### Modal interfaces

A modal interface demands immediate attention from the user. It typically appears as a dialog box or window that interrupts the current workflow, requiring the user to address it before continuing with the main application. Modal interfaces are useful for focusing the user's attention on critical tasks or information that cannot be ignored.

#### Key characteristics

- Exclusive Focus: Captures all input, blocking interaction with the rest of the application until the modal task is completed.
- Mandatory Interaction: Requires users to interact—by providing input, making a decision, or acknowledging information—to proceed.
- Interruptive Nature: Temporarily halts the main workflow to ensure certain actions are taken before moving forward.

#### When to use modal interfaces

- Immediate Attention Is Required: For critical warnings or errors that cannot be ignored.
- Sequential Task Flow Is Necessary: When specific input is needed before proceeding.
- Preventing User Errors: To confirm actions that may have significant consequences.

#### Examples

- Save Confirmation: When closing a document, a dialog asks if you want to save changes before exiting.
- Error Notification: An alert informs you of a critical issue that needs immediate action, such as a security breach.
- Login Prompt: A dialog requires authentication before accessing certain features or areas of the application.

---


### Modeless interfaces

A modeless interface allows users to interact with multiple windows or dialogs simultaneously without locking the application into a specific mode. This approach provides flexibility, enabling users to switch between tasks as needed without interrupting their workflow.

#### Key characteristics

- Non-blocking interaction: Users can continue working in the main application while the modeless interface is present and available on the screen.
- Flexibility: Supports multiple tasks and workflows without forcing a particular sequence.
- Complex State Management: While appearing stateless to the user, the application manages multiple states behind the scenes to maintain seamless interaction.

#### Complexity in Design and Implementation

- State Management Complexity: Modeless interfaces often require intricate state management. The system must handle multiple states and contexts simultaneously, ensuring that actions in one part of the application do not adversely affect others.
- User Experience Challenges: Designing an intuitive modeless interface can be challenging, as users may need guidance to navigate multiple concurrent tasks without confusion.
- Development Effort: Implementing modeless interfaces demands more sophisticated coding practices, including handling asynchronous events, concurrency, and potential conflicts between different user actions.
- Testing Complexity: The increased number of possible interactions and states requires extensive testing to ensure stability, usability, and that no unforeseen issues arise from concurrent operations.

#### When to Use Modeless Interfaces

- Enhancing Productivity: Provide access to tools and features without interrupting the primary task.
- Providing Reference Material: Keep helpful information accessible while performing other activities.
- Supporting Complex Tasks: Allow users to manage multiple activities seamlessly.

#### Examples

- Tool Palette: Floating toolbars in graphic design software that remain accessible while you work on a project.
- Find-and-Replace Panel: Search tools that stay open while you edit documents, allowing continuous searching without reopening the dialog.
- Background processes: File downloads or installations that run while you perform other tasks, with progress indicators (and/or actions like “Cancel”) you can check without stopping your work.

---


### Technical considerations

Understanding the technical implications of modal and modeless interfaces is crucial for making informed design decisions, especially regarding state management and implementation complexity.

#### Statefulness vs. Statelessness

- Modal Interfaces: Introduce a new state in the application that must be resolved before returning to the previous state. This stateful nature simplifies some aspects of design and implementation because the user's possible actions are limited during the modal interaction.
- Modeless Interfaces: Require the application to manage multiple states and contexts simultaneously. This increases complexity in both design and code, as the system must ensure consistent behavior across different components without interfering with the user's workflow.

#### Event and Focus Management

- Modal Interfaces: Simplifies event and focus management implementation by directing all input to the modal dialog until it is dismissed. Requires regular testing from various input devices to ensure an accessible experience.
- Modeless Interfaces: Requires careful handling of events and focus to manage inputs from multiple sources. Developers must ensure that interactions in one part of the application do not negatively affect others.

#### Development Complexity

- Modal Interfaces: Generally simpler to design and implement due to their linear nature.
- Modeless Interfaces: More complex to design and implement because they must handle multiple states and interactions without causing conflicts or confusing the user.

---


### Making the Right Choice

Choosing between modal and modeless interfaces depends on the application's goals, the desired user experience, and the complexities involved in implementation. Designers must balance the need to present capabilities without overwhelming users, considering both the benefits and challenges of each approach.
Modal interfaces are effective for tasks requiring sequential input or immediate attention, offering a strictly-guided UX and simplicity in implementation. Modeless interfaces, while more complex to design and develop, provide flexibility and can enhance productivity by allowing seamless interactivity across a variety of components.
Making the right choice leads to a more intuitive and satisfying experience, ultimately enhancing the outcome to all of us who are using these products. For a deeper dive into the philosophical aspects and design considerations, refer to Designing modal vs. modeless interfaces, which explores how these concepts influence user experience.

---

# Designing: Modal vs Modeless

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/designing-modal-vs-modeless
- **Tags**: ui, ux, development, design, product

When designing user interfaces, one of the most critical decisions is whether to implement modal or modeless interactions. While defining these terms helps us understand their roles, the real challenge lies in applying them effectively in UI/UX design. This article delves into the design considerations for modal and modeless interactions, ensuring a smooth and intuitive experience for users.

#### Understanding the User Journey

In user experience (UX) design, every interaction must be purposeful. Modal windows encourage users to complete a task before moving on, while modeless windows give users the flexibility to continue working without interruptions. Deciding which to use depends on the user’s journey and the task at hand.

---


### Modal interfaces

Modal interfaces guide users to focus on a specific task or decision, ensuring immediate interaction and attention.

#### Benefits

- Clarity and focus: By isolating a task, modals help users concentrate on important decisions without distractions.
- Error prevention: Requiring confirmation for actions reduces the risk of unintended consequences.
- Guided interaction: Assist users in navigating complex processes step by step.
While modals offer several benefits in focusing attention and preventing errors, they also introduce some potential downsides.

#### Drawbacks

- Workflow interruptions: Modals can cause frustrating disruptions.
- Perceived loss of control: Users may feel their autonomy is diminished when forced to interact with a modal.
- Desensitization risk: Overuse of modals may cause users to ignore them, reducing their effectiveness.

---


### Modeless interfaces

Modeless interfaces offer freedom, allowing users to engage with different aspects of an application as they prefer, without forced interruptions.

#### Benefits

- Flexibility: Users can customize their workflow, enhancing satisfaction and efficiency.
- Continuous workflow: Reduce unnecessary interruptions, promoting a natural interaction with the application.
- Multi-faceted input: Support complex tasks that require simultaneous access to multiple tools or information sources.
Although modeless interfaces bring flexibility and continuous workflow, they do come with certain challenges.

#### Drawbacks

- Potential overwhelm: An abundance of options may confuse or overwhelm some users.
- Increased cognitive load: Managing multiple tasks simultaneously requires greater mental effort.
- Learning curve: New users might find modeless interfaces less intuitive initially.

---


### Balancing modal and modeless approaches

The key is understanding when to apply each approach to best serve the user's needs and the application's goals.

#### Guidelines

- Context is key: Use modals for critical actions that genuinely require immediate attention within the application's workflow.
- User-centered design: Consider the target audience's needs, expertise, and preferences when choosing interface styles.
- Minimize cognitive strain: Provide clear pathways and avoid overwhelming users with too many options.

#### Impact on development and cognitive load

- Development effort: Modeless interfaces often require more complex programming and testing to ensure users can interact smoothly.
- Cognitive considerations: Designers must be mindful of the mental effort required by users, aiming to simplify interfaces wherever possible.

#### Making informed design decisions

- Empathy in design: Understand how users feel when interacting with the interface, and strive to meet their expectations.
- Feedback integration: Incorporate user feedback to refine the balance between modal and modeless elements.
- Iterative improvement: Continuously assess and adjust the interface to improve usability and satisfaction.
Regularly gather feedback from both new and experienced users to ensure that the balance between modal and modeless elements aligns with user expectations and usability.

---


### Conclusion

The thoughtful use of modal and modeless elements can create user experiences that are both intuitive and efficient. By balancing guidance with autonomy, designers can empower users and make every interaction feel purposeful.
The ultimate goal is to support the user's journey, making it as intuitive and empowering as possible. By considering the philosophical implications of modal and modeless interfaces, designers can create applications that respect user autonomy while providing necessary guidance.
> For a foundational understanding of these concepts, refer back to Defining modal vs. modeless interfaces, which outlines the technical differences and use cases of modal and modeless interfaces.

---

# Employee Turnover

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/employee-turnover
- **Tags**: culture, career, conflict, burnout, workforce

No one is expected to stay working the same job forever. Even in careers where people hold the same title throughout their lives, it's common for employees to move between companies in the same industry. Employee Turnover is an umbrella term for employees leaving their current position, be it to another position in their company, a new company in the industry, a new industry, or no job at all. It can be anything! Employee turnover tracks individual people moving through the working world. Companies can track their turnover rates to better understand employee satisfaction and workplace trends. A high turnover rate might relate to problems within the company that are driving people to leave. 
Employee turnover is broken into voluntary and involuntary turnover, and understanding the causes of each helps identify opportunities to increase employee retention and improve company culture.

### Employee Turnover: Voluntary and Involuntary

- Voluntary Employee Turnover occurs when an employee willingly leaves their position. Common causes include relocation, education, personal reasons, changing positions or careers, and dissatisfaction. 
- Involuntary Employee Turnover occurs when an employee is forced to leave their position. Common causes include layoffs, firing, and the end of a temporary job.
While the majority of turnover is voluntary, the balance between the two and the specific reasons employees leave provide valuable insights into workplace dynamics and organizational health.  Every company has its own ideal turnover rate, and figuring out that sweet spot helps analyze whether the current turnover is at a healthy level. High turnover rates might be a symptom of employee dissatisfaction in the workplace. 

### Employee Turnover: Effects

Certain aspects of employee turnover are easily quantifiable, while others are more difficult to put to paper. A high turnover rate affecting company morale and cohesion might also mean there are fewer senior employees in the company that have higher salaries and benefits packages, reducing payroll expenses. If a company is known for its layoffs, they might inspire increased short-term productivity as employees, fearful about losing their job, work harder to stand out.  
A dangerously high rate of employee turnover can sometimes go undetected in a company if they are focused on the numbers and not company morale and cohesion. Teams take a toll when members leave. Productivity dips as remaining members take up the slack or new employees are trained. A high rate of employee turnover can, however, be beneficial for companies in the short term. Fewer employees save them money. Hiring is a future cost, whereas voluntary or involuntary turnover is an immediate gain. 
For a company, high rates of employee turnover can hinder productivity, decrease employee satisfaction, and lead to increased future hiring costs. 
For employees, the decision to leave a company is often very complicated. Voluntary turnover happens for a lot of reasons, including: 
- Career change. Employees change fields to pursue other jobs. Some go back to school, others go straight to another job. 
- Family/personal necessity. Any number of family or personal factors might inspire an employee to leave their current post. 
- Job dissatisfaction. Here is where companies have the most agency. Employees who are unsatisfied with their jobs are more likely to look for employment elsewhere. 
An abundance of employees leaving due to job dissatisfaction is a big problem within a company. Unaddressed, high turnover driven by job dissatisfaction breaks down morale and productivity, whether due to a toxic work environment, high-stress roles, poor management, or other systemic issues. Turnover driven by dissatisfaction becomes a significant issue when it dominates the reasons employees leave. 

#### When is it time to leave your job? 

The brain pushes and pulls, sometimes tempting you with the sweeter and greener grass in another pasture, other times locking you down with the fear of the unknown and the uncertainty that comes from entering the job search. If you’re feeling restless and wondering if it’s time to move on, take a moment to think carefully about your decision. What specifically is driving your desire to seek something new? Could there be opportunities to address those challenges and improve your current situation?
A little investigation into what is driving employees to leave pays great dividends. Is there a specific problem within the company? Investing energy and resources into pinpointing and resolving problems can prime employers and businesses to achieve and sustain optimal health and productivity. Good enough, perhaps, to change the equation of whether or not it’s time to leave your job! There are, of course, many great reasons to pursue another career. If you need help coming to that decision, feel free to drop us a line! We are always happy to help make work feel better. 

---

# Fighting Work Dissatisfaction

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/fighting-work-dissatisfaction
- **Tags**: stress, burnout, career, culture, workforce, health

People work. A million details make every job unique, but nearly everyone clocks in. For Americans over 25, the average weekday hums along at just over eight hours. That’s a third of their day—yet too many trudge through it dissatisfied, disengaged, quietly miserable. This article digs into that gloom and pulls out ways to fight it, leaning on Patrick Lencioni’s The Truth About Employee Engagement for a roadmap.

### Small Changes, Big Results

Companies crave productive workers who—ideally—don’t hate their jobs. The logic’s simple: happy employees give more. But how do you get there? Lencioni pins it on three culprits dragging satisfaction down:
- Anonymity: People shine when they’re seen and valued.
- Irrelevance: They thrive when their work matters.
- Immeasurement: They engage when they can measure their wins.(Author’s Note: No, “immeasurement” is not a word. Lencioni insists on it, so, with great reluctance, I will use it as well.)
In The Truth About Employee Engagement, he argues that tackling these three points turns misery into meaning. Let’s break it down.

#### Anonymity: The Invisible Worker

Feeling like a ghost at work kills drive. Take John, a glass etcher on a factory floor with 99 others. From 9 to 5, he scratches away. The top 10 producers get a bonus; the bottom 10 get a warning. John’s no star, so he aims for 89th—safe, unnoticed. His manager barely knows his name, let alone his story. His co-workers? Strangers. He’s a cog, and he acts like it—disengaged, coasting.
Anonymity is a trap. When no one sees you, why bother? Effort flatlines, mistakes creep in. John’s not alone—too many fade into the background, their satisfaction tanking with their output.

### Irrelevance: Does This Even Matter?

When work feels pointless, motivation evaporates. Money’s nice, but it’s not enough—ask any celebrity. Actors, musicians, athletes—they rake in millions, yet some still feel adrift. Why? Relevance isn’t cash; it’s impact.
Employees need to see who they help—co-workers, customers, someone. For celebrities, fans are customers: a song lifts a mood, a game sparks a kid’s dream. Charity amplifies it—time or dollars they give trace back to their gig. At your desk or on the line, it’s the same game. A manager dropping by to say, “Your work saved my day,” can flip the script. It’s proof you’re not spinning wheels.
Managers, challenge yourselves to help employees see how their job impacts customers and their co-workers. Employees, challenge yourselves to do the same! 
In The Truth About Employee Engagement, Lencioni gives an example of restaurant workers. The cooks, Joaquin and Kenny, were feeling pretty disengaged from their work until he reminded them of its importance. When they work hard the customers and servers are happier. The customers compliment the servers on quick service, average tip percentage goes up, and the servers are less stressed. 

### Immeasurement: Measuring What Counts

Then there’s immeasurement. Lencioni writes, “The key… lies in identifying those areas an employee can directly influence, then tying measurements to the people they serve.” Big metrics like revenue, stock price, and long-term projections are fog; they’re too vast to grip. Real measures hit close: a cashier tracking smiles per shift, a coder counting new and improved branches.
Start with relevance. Ask: Who’s helped? Then, peg a number to it. Employees can tally it daily, weekly, or whenever it works. It’s their stake, the proof they are not just clocking hours.

### Rooting Out Misery

Are anonymity, irrelevance, and immeasurement the unholy trinity of job woe? Maybe. Even if not, working to make employees feel like they are part of a team with measurable goals will improve overall morale. At En Dash, we are passionate about this, delivering insights and tools to make work feel better. Ready to rethink your workplace? Let’s talk.

---

# Grass is Greener

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/grass-is-greener
- **Tags**: conflict, burnout, career, workforce, culture

The grass is greener bias is the tendency to overestimate the appeal of alternatives while undervaluing the positives of the current situation. In our professional lives, it pops up when we are feeling dissatisfied with our jobs. It is a nice escape to imagine how great things could be at a different job. Sometimes, that feeling gets so strong that it pushes us to look for a new job. There must be something better out there, right? 
Well, maybe! There are a lot of reasons to look for a new job, but it’s important to look for the right reasons. In this article, we are going to talk about the grass is greener bias and how understanding it can help you pursue greater work satisfaction whether you stay at your current spot or move to a new one! 

### The Grass is Greener Bias: Making Intentional Choices

The grass is greener bias has two core principles: 
- Overvaluing something new
- Undervaluing something current
The brain idealizes alternatives while glossing over the positives of the current situation. The bias comes in with the belief that other opportunities—like a new job, a new car, a new “________”—are better. In this, we are optimists. Let’s stick with job as the main example. When evaluating a new job, there are countless unknowns, like how much you’ll like your co-workers or your manager, how polished your workflow is, how nice the coffee is, how comfortable the chair, etc. It can be anything. We have a tendency to inset good outcomes into these unknown variables when looking at a new position. Especially when it’s something lacking in our current spot. 
Let’s say John works at Company X and has a task management system that results in him working overtime to stay on an unrealistic schedule. In his brain, that new position at Company Y must have a better task management system, a conclusion he is comfortable arriving at without any evidence. The two core principles of this bias work together exceptionally well to artificially widen the perceived satisfaction from his current and new situation. 
This bias becomes more complicated because there are many times when there is a real, not just perceived, gap in your current satisfaction and what you might find in a new position. This is why we champion making intentional choices. Understand that this bias does affect your decision-making, and look for areas where it may have led you down the path of idealizing the future or downplaying your current situation. 

### Tools for Decision-Making

Though decision-making comes with its challenges, there are a lot of tools you can leverage to help you out along the way. 
- Write Lists and Add Weight. Writing out the pros and cons of your current situation helps put it in perspective. Adding weight to those items (i.e. salary is more important than coffee) helps visualize your feelings. 
- Six-Month Rule. Commit to improving your current situation for six months before making any major changes. You can start this anytime! Preparing this in advance makes it easier to make decisions in the future. 
- Talk to Friends, Family, and Co-Workers. Outside perspectives are incredibly valuable, and coworkers have their own perspectives in the industry. Gathering multiple opinions can temper your own and help you choose the right path forward. 
- Look to the Future. Consider how a decision would feel in a week, a month, a year, or five years. Try to make relatively realistic assumptions and explore how you would feel. 

---

# Meetings: A Recipe for Success?

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/meetings-a-recipe-for-success
- **Tags**: async, career, workforce, remote, culture, communication, teamwork, conflict, collaboration


#### Meetings are critical. Critical for success or a critical obstacle, well, that depends.

Everyone has something to say about meetings. They are essential parts of team workflows but can quickly tip from “helpful, insightful with actionable takeaways” to “I have more important things to do”. The trouble comes when an overabundance of meetings leads to more stressful deadlines. If you have a lot of solo work and have a lot of meetings spread throughout the day, it becomes very difficult to focus and complete your tasks.

### Why are Meetings so Important?

Meetings offer time for teams to sync up. Modern communication tools are fantastic, allowing people to work from anywhere and communicate at any time of the day. That being said, none of them replace the power of meetings.
Meetings are a great way to solve blockers. Goals change, and spending too much time working in a vacuum leads to ever-increasing risks that the work you do is no longer aligned.
So, meetings help keep teams synced up, working towards the same goal, and, especially when working remotely, a time to see your coworkers. This all sounds good, but meetings do take you out of the workflow you’ve established during the course of the day. This is not necessarily a bad thing. Almost no one works fully focused from the moment they clock into the end of the day. That herculean effort should not be expected of you, leaving time in your day for meetings and other distractions.

### What Makes Meetings a Drag

Think about the last meeting you’ve had. At its conclusion, did you jump right back into your current project, or was there a little downtime before you got back into a productive workflow? If you dove right back in, then heck yeah. That’s awesome. You’ve evaded the phenomenon of meeting recovery, a concept explored in a recent study as the time it takes to “recover” from a meeting.
So, the next time you come out of hours of back-to-back meetings, make sure to give yourself some time to recover. Steeling your will and jumping right into work heightens the risk of burnout, rendering even the strongest workers helpless to go any further.
Meetings can get in the way of solo focus time. An abundance of meetings slice up the workday so much that it is hard to sit down for extended solo work sessions.  This is stressful, especially when your current project has a lot of solo milestones. 
This feeling is compounded when it doesn’t seem like they need to be at these meetings, anyway. Sitting, in-person or remote, in what feels like an unnecessary meeting will make that participant pay less attention, thinking about their own work, and count the seconds until they can get back to it. This happens when employees feel like they can’t say no to a meeting invite, even if they have a perfectly good reason.

### How to Improve Meetings for Your Team

There is no panacea for meeting improvement. Alas! Perfecting meetings for your team requires a custom solution that takes into account all the unique variables that make your team or your business its own. There are many potential ways to better the meeting culture in your company, but without spending the time to figure out what works best, you may implement great solutions to nonexistent problems. For instance, you can try:
- Prioritize Planning—Make use of the 40-20-40 rule, spending more time preparing for the meeting and executing meeting takeaways.
- Small Meetings—Meetings are expensive! Every person adds to the meeting’s cost. Choose your participants carefully, and separate necessary and optional meeting participants.
- Office Hours—Non-mandatory meetings at a specific time for people to meet if they need to. This lets people meet in a flexible environment where team members can talk in advance about meeting topics and ping key individuals to join. 
- Defined Meeting Agendas—Straying from the task at hand extends meetings longer with no additional benefit.
There is no one-size-fits-all treatment for bettering the meeting culture in your company. At En Dash, we specialize in providing solutions to your company’s problems. Whether you require a custom software solution or just some consulting expertise, feel free to reach out so we can help you take the first step in the right direction.

---

# Remotely Equitable

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/remotely-equitable
- **Tags**: remote, collaboration, teamwork, workforce, async


### BC - Before COVID

At the beginning of the pandemic, I worked for a company that allowed one day per week remote, pretty much across the board. When hired, I negotiated two days remote, but I was an anomaly (in a not-so-popular way). I wasn’t the only exception to the rule however. There were a handful of employees across the company who were hired as full-time remote or allowed to transfer to a full-time remote status, usually due to their physical location being too far from the office. This company had the best of intentions, and they were really striving to do what the employees needed. However, the inconsistency in remote work statuses within and across teams bred more than a little contention. Enter COVID, the great equalizer of remote employees. 
The COVID-19 pandemic certainly didn’t invent remote work nor did it create the many wonderful upsides or the common pitfalls associated with it. However, it did bring the swirling ecosystem of pros, cons and neutrals to the forefront. Companies across the globe had to dust off their remote work policies, or create them from scratch, to figure out ways to make remote work scalable and applicable to their entire workforce. When everyone was first sent home some companies found the switch relatively easy, some not so much. Some companies didn’t have to switch anything because they had been remote all along. 

### Fully Remote for the First Time

About a year into the pandemic, I left my analyst job at a midsize company to take on the life of a consultant at a tech start up in a fully-remote-no-intention-of-ever-being-in-person role. I was equal parts excited and intimidated at the prospect of never having an office to go to. In those early months, our company talked a lot about how we individually viewed remote work and the influences on those views. Rework and Remote (by the creators of Basecamp) have had a huge impact on how our team approaches work; talk about revolutionary! I started challenging the truths I had always accepted about work and office work in a way I hadn’t expected. This new world of fully remote really got me thinking about how difficult it can be to implement effective remote work policies how we could make them simpler. The answer is equity. 

### Equity is different than equality. 

Equality is the source of the blanket policy; everyone gets treated the same way. It is not a bad thing in theory, but because of an increasing trend towards embracing individuality, it is really rather difficult to implement. The blanket policy often requires exceptions to be made for one reason or another, and, under the banner of equality, these exceptions can be incredibly difficult for other employees to accept. 
Equity solves this problem because it casts an eye to treating people as individuals who need different things. The ideas around policy at this new company were based on equity. Need to work remote full-time to be your most productive self? Sure, go for it. There were no hangups about productivity or trust or any of the push back I had seen regarding remote work elsewhere. 
The philosophy was simple: only hire people you trust to do the work you hired them to do, and assume they are doing just that until there is evidence to the contrary. 
With this approach, there is really no room for contention because each person works to figure out how remote work can work for them and the company works to support that. Each employee has the opportunity to establish their own policy around remote work and then to be transparent about if that policy is working over time or if it isn’t. The employer has that same opportunity. 

### But will it work on a large scale? 

Now, it may seem like this philosophy isn’t scalable, but why not? The answers most employers will give center around fear of losing the semblance of “control” or “oversight” of employees and their productivity. But it begs the question, how much control does the office setting really offer? If we are honest, we find plenty of ways to escape productivity while physically in the office. Regardless of precautions taken by the employer, there are myriad ways employees can be unproductive in the office. Additionally, those aforementioned precautions often breed mistrust and a feeling of being watched and monitored that most professionals find insulting and belittling. Other answers for “why not remote?” center around the challenges of being collaborative while remote. It seems that the last year would be more than sufficient evidence to the contrary. Many companies, especially in the tech industry, didn’t skip much of a beat when their entire workforce transferred to full-time remote. 

### Bend and Not Break

The philosophy of equitable remote work can feel revolutionary especially to companies that have been around long enough to have the “we have always done it this way” syndrome. It could be that a blanket remote work policy has worked well or well enough for many workplaces; however, change is upon us. Remote work is here, and many of us will never work in an office the way we used to. Companies all over the world are trying to put the toothpaste back in the tube as they frantically look for ways to entice employees back into the office. Many will face a significant loss of talent. Organizations that are ready to implement, but more importantly EMBRACE, a culture of remote work will have a good chance of retaining their existing workforce and are poised as soft landings for people fleeing the traditional brick and mortar model. Adopting an equitable approach to remote work policies gives companies, regardless of size, the flexibility to bend and not break as the workplace changes in drastic and unprecedented ways. 

---

# Respecting Boundaries: Building a Balanced Work Culture

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/respecting-boundaries-building-a-balanced-work-culture
- **Tags**: teamwork, conflict, collaboration, communication, culture, remote, workforce, async

Picture this: it’s your day off. You decided to take a day off to catch up on life. You have doctor’s appointments, errands to run, and catching up around the house. Life has been hectic (as it always is), and you finally decided to take the time for yourself. Suddenly, you get a phone call from work. A ping on your phone, and someone wants to jump on a “quick call.” And now… you’re working. Your day off has turned into a few “quick calls” and you no longer have the opportunity to take care of yourself and your family.
Now, picture this: it’s your day off. You run your errands. Your house is clean. You have made it to all of your appointments, and dinner is made. You sit on the couch at the end of the night, turn on your favorite show, and relax. You are re-energized. You don’t look at your email, and you don’t even know how many messages you’ve received. You are able to separate your life from your work, and you are refreshed. You are ready to take on your workday tomorrow and at peace with the time you took off.
Who do you want to be?

### Why set boundaries?

While work is a large part of our lives, we can all agree that there are times where we are burnt out, tired, or need a break. How can we prevent that from being a daily struggle? Easy: setting boundaries. OK, maybe not easy, so let’s talk about it.
Every workplace has a different culture. There are workplaces where 
- You work 60 hours but get paid for 40 hours
- You work 40 hours and get paid for 40 hours, but the stress is excessive
- You work from home, so you’re really always on the clock
- And the list goes on…
In any workplace, there are opportunities to set boundaries and protect your personal life from meshing with work life. With boundaries and expectation setting, you will allow yourself more time and freedom for:
- self-care
- hobbies and personal growth
- family life
And when you are at work you will be able to:
- increase focus time
- increase efficiency and productivity
- reduce burn out and exhaustion

### How to start setting boundaries

Start with your team. You are likely not the only one feeling overworked and burnt out. Don’t worry about starting small. It’s a good sign if your co-workers seem surprised that you are even bringing it up. It is (usually) not with malice that your team pulls you into a call or messages you outside of work hours. Setting boundaries with your team makes it easier to enforce the boundary when the time comes. 
There is no prescription or one size fits all. This practice is based on what’s important to you, your values, your team, and your team’s goals. This will allow you to prioritize those boundaries, and keep adjusting towards what feels right and what works. Once you identify these goals and values, allow that to drive the boundaries you set for yourself.
Setting boundaries with your team is one thing, but don’t forget to set boundaries with yourself, too. There is a time and place to go the extra mile, but if it becomes the norm, it absorbs your time (and the life half of your work-life balance).

### Check in with yourself

After setting these boundaries based on your goals, regularly check in, monitor, evaluate your own sense of comfort and progress. Being uncomfortable is normal at the beginning of this practice. Everything can be adapted and changed based on yours or your team’s needs.
- Check in: is your work life balance improving? How are you feeling?
- Monitor: are you spending the correct amount of allocated time at work and at home? What’s actually happening?
- Evaluate: are you feeling less burnt out? Are your boundaries doing what they’re supposed doing?

### Check in with your team

Everything starts with a conversation. Your co-workers are (fortunately) not mind readers. It is acceptable to vent about Jane who never makes a new pot of coffee when she finishes it and John who always comes to meetings 5 minutes late. That being said, it is important to know when little peccadillos become proper problems—when Jane starts drinking the coffee from your cup and John misses meetings entirely, only to schedule one later so you can catch him up. 
If you are uncomfortable with the way certain things are going, it is time to talk about them. Depending on what it is, your first point of contact could be your co-worker, your manager, or someone from human resources. Starting a conversation like this is hard, but it is important. When you are talking to them, remember to be open and honest about the boundaries you need to set. Be transparent. Tell them what’s bothering you and what needs to change. You don’t need to be rude about it, but you don’t want them to be confused, either. 
Be patient when talking to your co-workers. This is not an instant change. It will grow and flourish like a well-kept garden, but expect changes too soon and your buds will never bloom. 

### Building Boundaries

Everyone’s position is unique. Think about the boundaries you need to feel better in and out of the office. Whether you are in-person, hybrid, or fully remote, setting the right boundaries helps you stay productive, evade burnout, and increase your overall job satisfaction. Need an assist? Drop us a line! We are happy to help.

---

# Should you go?

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/should-you-go
- **Tags**: growth, career


#### A guide to attending conferences and getting the most out of them when you go back to your daily usual. 


### Step 1…YES! You should go!

Earlier this year, I had the opportunity to attend a Product-Led Summit hosted by The Product-Led Alliance. This organization hosts many conferences and summits all over the world, this one was in Austin. It was my first time traveling without my team and attending a conference like this on my own. Leading up to it, I was pretty nervous and didn’t know what to expect. Afterwards, I’m so grateful I stepped out of my normal routine and went. The experience was incredible and yielded two jam packed days of insightful speakers and rich conversation. 
I got back on the plane to Baltimore early Saturday morning feeling energized and renewed, eager to share my learnings with my team, use some of the tools that were featured, and apply new mindsets to our own product development efforts. I had a host of new LinkedIn connections and my feed was newly full of inspiring posts from speakers who had just sort of blown my mind in the 48 hours preceding. 
Now, a week later, I’m reflecting on the whole in-person conference experience. We didn’t even have the option for so long, and now people seem to be flocking to hotels, convention centers and speaker halls to reconnect and to learn from each other. It’s an amazing thing. Sure, the level of energized that I felt immediately after the conference dissipates a bit with each passing day, but that being said, it’s on me to keep it going. 

### Step 2…Keep it going!

From meeting with colleagues to share resources to connecting with CEOs on LinkedIn to signing up for free trials of new software, it’s up to me to incorporate the electric atmosphere of a conference into my day-to-day flow. But how do I do that? Anyone who attends a conference faces the challenge of capturing that lightning in a bottle and drawing from it whenever the daily grind lulls you back into your comfort zone. It has me thinking about HOW you keep the momentum from a conference going. Here are some things I have come up with as well as some steps to take DURING the conference to enable these post-conference activities. 

#### Engage your Network

During the conference: 
- make note of speakers you want to connect with and if you have time send them an invitation on LinkedIn with a reference to something from their talk that resonated with you
- engage with people in the audience before and after sessions to find other people to add to your network
- during any interactive times, talk about how you will apply what you learned to your day to day and seek to understand how other conference attendees will do the same
- if you can bubble up their perspective on work issues you may have or vice versa try to do so 
Immediately after the conference
- thank speakers for the talks and try to include a note about what you loved about their talk or a question their talk may have sparked in you 
- message a few closer connections about how much you enjoyed spending time with them or something you learned from them 
In the following weeks
- schedule a virtual coffee with someone you met
- send a LinkedIn message to someone you may have chatted with during the conference to check in on something you discussed with them during the conference

#### Materials 

During the conference:
- Take notes! Even if the slides and recordings will be shared out, take notes of the things that leap out at you during each session 
Immediately after the conference:
- If you have the ability to access the conference materials after the fact, be sure to do that and store them somewhere that will allow you to access them later
- Share information from the conference with coworkers. This can take many different forms depending on your working model and the culture of your workplace
In the following weeks: 
- Assemble resources shared from the conference in a shared google drive. If some content made you think of a specific person who would benefit from it, don’t be shy about directing them to the exact talk, resource, etc. AND offer to talk about it with them
- Coordinate a lunch and learn or a brown bag to share information you learned from the conference with your team, department, organization, etc. 
- Try to apply one new thing you learned each week as best you can
- Refresh yourself on your favorite moments from the conference by reviewing your notes, speakers’ videos or presentations

#### New Tools

Conferences inevitably have sponsors which means that any conference attendee will leave with armfuls of SWAG and a brain-full of new tools to make work easier. Each sponsor likely has a new tool that they are advocating for and many speakers will offer tools as part of their talk. 

### Step 3…ABL: Always Be Learning! 

Whatever your motivation for attending a conference, your mindset whilst there and afterwords has a lot to do with how much you will get out of it. Approaching a conference with the attitude of “How much can I learn here?” will yield much more powerful and lasting results than one of “ugh, I don’t feel like doing this!”. This also applies in the days, weeks and months following a conference. There are many small things you can do with regularity that can help you develop or strengthen your learning mindset. Here are a few that I find helpful:
- Seek out further learning on topics that resonated with you from a recent conference or other learning opportunity
- Set aside 10-30 minutes a day to read something that can strengthen a burgeoning skill 
- Enroll in a self-paced class or workshop (there are SO MANY free ones) and slowly chip away at it by blocking a little calendar time each week
- Pick a topic you know nothing about but are curious about and learn one new thing about it each week
Remember, being a lifelong learner takes intentionality once we are out of formal schooling. Often our days seem so busy and our schedules so jam-packed, that our learning experiences are quickly regulated to those that are NECESSARY as opposed to JOYFUL. Both have their place, but a combination of the two is a great way to cultivate a deep passion for learning and by extension, work. 

---

# Small Steps

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/small-steps
- **Tags**: growth, culture, career

My biggest takeaway of my thirties is that…you don’t have to dance with the one that brought ya…at least not all night. Despite the degrees on my wall being very education-focused, I find myself building an incredibly fulfilling career in the technical world. Whenever I casually mention that I taught high school English for a decade, people look at me incredulously wondering…how on earth did you end up here? The answer: a winding road with some calculated risk-taking. Life, I’m finding out more and more, is not linear. 
Where you are heading in the beginning isn’t where you have to end up. I’m a Product Consultant for a software development company, but I use my ninth grade English teacher skills every single day. Back in those public school days, I could never have predicted where I would land, but a series of taking the next best step led me, and continues to lead me, on some incredible adventures. 
My first step out of the classroom came from a master’s degree in curriculum development. I took a job as an instructional designer to write curriculum for adult training. Once I landed in the training company, I found that a large portion of my teaching skill set transferred to this new work environment. I worked on several projects in those first few months, but the one that excited me the most was building internal training materials for an IT modernization project. It was my first introduction to business process management, and I was hooked. 
Thanks to a few supportive women in tech, I got my foot in the IT door with a business analyst role and learned as much as I could as fast as I could. In this role, I again called on skill sets amassed from previous experience in a field seemingly unrelated to business analysis. A few years later, I couldn’t remember a time where I wasn’t a BA. I had hit a little bit of a plateau after a seriously steep learning curve, and I was ready for a new challenge. Enter a small tech startup in need of some product consulting and scrum mastery. After contracting with the start up for a while, and grabbing a certification or two to provide some formal support for my work experience, I made the leap to a consulting job. 
A little over a year in as a consultant has me reflecting on my journey here. Along the way I have had many conversations with so many people who feel handcuffed to their current position. I hear time and again the fear of the unknown, the concern about whether skills will translate from industry to industry or from one position to another or a general confusion about how to take the first step in a new direction. These are all completely understandable sentiments when thinking about changing careers. It can feel incredibly overwhelming to even think about that sort of overhaul, but it may help to reframe a change like this. Instead of “changing careers” perhaps we consider a more tempered approach. I like to call it shape shifting. In my experience, it looks a little something like this: 

### Shape-Shifting Steps

1. List out your strongest skills. These can be incredibly specialized or more industry agnostic
1. List out the parts of your job that fulfill you the most. For example, maybe you are a teacher and you love the people part of your job, but lesson planning is your worst nightmare. Focus on the people part. 
1. Take a look at industries that rely on a combination of your strongest skills and the parts of your current job that you enjoy.
1. Update your resume with language that is commonly used in the lexicon of the industry you find appealing.
1. Ask two trusted people to do “cold reads” of your resume
1. Look to see if there is a logical certification to obtain that formalizes your body of knowledge in some way OR look for training to bolster a skill set in an industry that appeals to you.
1. Cast a wide net.
1. Interview often. 
1. Be selective.  

### The Bottom Line

The bottom line is: you are not stuck. You can make a change. If a big change is too overwhelming a thought, break it down into a series of smaller next best steps. At some point, you will come to a step you cannot reverse (ie leaving one job for another) but even that step isn’t binding. You can always just take another step. We spend so much of our lives working…we aren’t meant to be miserable while doing it. 

---

# Speaking the Same Language

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/speaking-the-same-language
- **Tags**: communication, culture, workforce, teamwork, collaboration

In both the workplace and the world, we often find ourselves speaking different languages—literally or metaphorically—which can create frustration and isolation. When we aren’t understood, it’s easy to assume incompetence or bad intent, when in reality, the root issue is often miscommunication.
Recently, I had the amazing opportunity to work with a client where almost everyone is bilingual. While technically the language of the office is English, a great deal of casual and professional conversation is conducted in Spanish. I have always considered my Spanish “passable.” When asked if I was “fluent,” my answer has always been, “Drop me off in a Spanish-speaking country, and I should be able to make my way home." After six months of working in a bilingual office, I am now considerably much more confident in my ability to conduct a conversation in Spanish. 
While my Spanish improved, I learned so much more than language skills. We so often make instant, unfair judgements about the value of teammates, expect everyone to speak clearly and confidently, and run into language traps because of slang and jargon that is not intuitively understandable. Allow me to offer some of these lessons learned in the hopes that you can avoid these miscommunication maladies moving forward. 

### Lesson 1: Judge less; listen more

The whole experience was incredibly impactful and made me reflect daily on the power of shared language. As we navigate the world, we constantly make judgments about our environment and the people around us. This is certainly an evolutionary holdover: we judge quickly to determine if elements in our surroundings pose threats. During this experience, I observed how expressed language plays a crucial role in our modern "threat assessments." Those who don't immediately and eloquently express their thoughts and ideas are often categorized as less valuable. This is undoubtedly unfair, even when we share a common language. In the case of this client, a language barrier was often at play. So how then can we judge the smartest in the room? Perhaps that's the wrong question. Maybe we should ask: should we judge so quickly? 
By intentionally placing our rapid judge-o-meter on a slower setting, we can first seek to understand rather than be understood. During one meeting, a team member hesitated before contributing an idea, clearly searching for the right words. Rather than moving on, we paused and gave them time, leading to a valuable discussion that might have otherwise been missed. By practicing active listening, asking clarifying questions, and slowing down the pace with which we move through our day, we can create an environment that is far more inclusive. If the past decade has taught us anything, it is that an inclusive space is always a more thoughtful, comprehensive and, ultimately, powerful space.  

#### TL/DR: 

- Snap judgments about others' contributions, based on surface impressions, can prevent us from recognizing their true value.
- Slowing down and practicing active listening fosters inclusivity and ensures valuable ideas are not missed.

### Lesson 2: Silent struggles take up a lot of space

In that same understanding vein, the experience has given me so much empathy for people operating in an English-speaking world for whom English is not their first acquired language. Our huge world is becoming smaller every day. We are more and more members of a global community in which there is an opportunity for rich discourse and exchange of culture, ideas, and language. The chances of encountering someone who speaks more than one language are high, and a lot of times we make assumptions about their abilities or intentions based on how they communicate in a shared language. 
What we don’t always see are the silent struggles beneath the surface—those moments when someone hesitates because they’re searching for the right word, or when they choose to stay quiet in a meeting because they’re unsure how to express a complex thought in their non-native language. These struggles can lead to missed opportunities, both for the individual and the team. The quiet battles people face with language can take up immense mental energy, making it harder for them to fully engage or showcase their true expertise.
The emotional and cognitive load of translating thoughts from one language to another is often invisible, but it's there, occupying space that could otherwise be used for creativity, problem-solving, and collaboration. What’s worse, when these struggles go unnoticed or unaddressed, they can lead to feelings of inadequacy or isolation, causing some team members to withdraw or disengage altogether. For teams that thrive on open dialogue and innovation, this is a significant loss. Recognizing these silent struggles is the first step. Offering empathy and creating a culture that encourages dialogue, regardless of language proficiency, can open doors to more meaningful interactions. Something as simple as allowing extra time for responses or encouraging a pause to gather thoughts can make a huge difference. 

#### TL/DR: 

- Language barriers can cause hesitation, missed opportunities, and mental strain, often going unnoticed but affecting both individual and team performance.
- Offering empathy and extra time for responses creates a more supportive and collaborative environment.

### Lesson 3: Shared language does not ensure shared understanding

Even when we share a language, true understanding can be elusive. Words are shaped by our personal experiences, cultural backgrounds, and emotional states—all of which color how we interpret and convey meaning. In a workplace setting, two people might use identical terms yet walk away with entirely different interpretations of a conversation. Shared language creates an illusion of mutual comprehension, but it doesn't guarantee we're fully grasping each other's perspectives.
During my time with a bilingual team, I realized that even in conversations conducted entirely in Spanish or English, misunderstandings still occurred. Sometimes these were due to cultural differences, other times because of assumptions about certain words or phrases. This taught me that real understanding transcends the words we speak; it requires active listening, asking clarifying questions, and making space for diverse interpretations. Only then can we move beyond simply speaking the same language to truly communicating and connecting. Additionally, many workplaces have two languages always in play: IT speak and business jargon. While there is greater and greater emphasis being placed on the power of bringing these two worlds together, in many organizations, the divide between IT and business teams can be just as wide as a language barrier. I’ve seen projects stumble because both sides used familiar terms, but interpreted them differently. By applying the same patience and empathy we use in a bilingual setting, we can bridge these internal divides as well. The practices employed in a bilingual office can easily be applied to misunderstanding between the worlds within an organization.

#### TL/DR: 

- Common language doesn’t guarantee mutual comprehension; words are influenced by personal and cultural experiences.
- Active listening and clarifying questions are essential to bridge gaps, especially between different organizational "languages" like IT and business jargon.

### Bridging the gap: Creating a space for understanding

Ultimately, this experience taught me that the key to bridging communication gaps is creating an environment where people feel safe to express themselves, even if they aren't perfectly fluent in the language of the workplace. Empathy, patience, and active listening are critical to overcoming language barriers, whether those barriers are literal or figurative. By approaching every interaction with the intent to understand rather than judge, we create a more inclusive and collaborative environment that values diverse perspectives. In the end, shared language is important, but shared understanding is even more vital. 
As our world becomes more interconnected, the ability to bridge communication gaps will only become more crucial. The workplaces of tomorrow will thrive on diversity, not just of language but of thought and experience. By fostering a culture of empathy and openness today, we’re preparing ourselves to meet the challenges and opportunities of the future. Ask yourself: How often do I assume misunderstanding is due to incompetence, rather than a gap in communication? Next time, slow down, listen more carefully, and create the space for real understanding. Your team, and the people around you, will be better for it.

---

# Start With an If: Feature Toggles

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/start-with-an-if
- **Tags**: development, product, delivery, agile, guide

Feature toggles don't require complex tools or infrastructure. They start with a single variable and an if statement using your existing deployment process.
This article covers a practical progression from basic on/off toggles, to audience targeting, and then to deployment-free changes, with realistic expectations at each step.

---


### The Core Idea

Deploy code to production disabled, then enable when ready. No long-lived feature branches.
```
ENABLE_FEATURE = false

if ENABLE_FEATURE then
    // new code
else
    // existing code
end if

```
This keeps the main branch (your primary production branch) deployable from day one. A deployable main branch supports continuous integration, minimizes merge conflicts, and accelerates feedback—foundations of trunk-based development. See Trunk-Based Development and Continuous Delivery for more on these practices.


---


### Getting Started


#### 1. Pick the Right Feature

Start with: UI label changes, buttons, error messages
Avoid (if new to feature toggles): Database changes, business logic, cross-repo work

#### 2. Basic Toggle Example

New homepage labels:
```
// components/homepage/labels.js
const ENABLE_NEW_HOMEPAGE_LABELS = false;

export const getHomepageLabels = () => {
  if (ENABLE_NEW_HOMEPAGE_LABELS) {
    return {
      heroTitle: "Discover Your Next Adventure",
      ctaButton: "Start Exploring",
      feature1: "Smart Recommendations"
    };
  } else {
    return {
      heroTitle: "Welcome to Our Platform",
      ctaButton: "Get Started",
      feature1: "Feature One"
    };
  }
};
```
Usage:
```
const labels = getHomepageLabels();
return <h1>{labels.heroTitle}</h1>;
```

#### 3. Deploy, Test, Activate

- Commit to main, deploy normally (feature off)
- Set true locally to test
- Set true and redeploy to activate

---


### Phase 1: Config in Code

Centralize toggles and introduce audience targeting.
Structure:
```
src/
  config/toggles.js
  utils/toggle.js
```
config/toggles.js:
```
export const TOGGLES = {
  ENABLE_NEW_HOMEPAGE_LABELS: {
    enabled: false,
    audiences: ['beta_users'],
    percentage: 10
  }
};
```
utils/toggle.js:
```
import { TOGGLES } from '../config/toggles';
import { getUserAudience } from '../auth';

export const isEnabled = (featureName) => {
  const feature = TOGGLES[featureName];
  if (!feature) return false;

  const audience = getUserAudience();
  const audienceMatch = feature.audiences.includes(audience);
  const percentageMatch = !audienceMatch && Math.random() < (feature.percentage / 100);

  return feature.enabled && (audienceMatch || percentageMatch);
};
```
Usage:
```
import { isEnabled } from '../../utils/toggle';

export const getHomepageLabels = () => {
  if (isEnabled('ENABLE_NEW_HOMEPAGE_LABELS')) {
    return { /* new labels */ };
  }
  return { /* existing labels */ };
};
```

---


### Phase 2: Deployment-Free Toggles

Once toggles are stable in code, move config outside the codebase to enable changes without deploys.
Option 1: Environment Variables (generally requires a restart)
```
ENABLE_NEW_HOMEPAGE_LABELS=true
HOMEPAGE_LABELS_AUDIENCES=beta_users
HOMEPAGE_LABELS_PERCENTAGE=10
```
Option 2: Database Flags (no restarts required)
```
INSERT INTO feature_flags (name, enabled, audiences, percentage)
VALUES ('ENABLE_NEW_HOMEPAGE_LABELS', true, '["beta_users"]', 10);
```
Cost: 2-second DB update, no restart.

---


### Quick Start

1. Add ENABLE_NEW_HOMEPAGE_LABELS = false
1. Wrap labels in if
1. Commit to main, deploy normally

---

Start with one if statement. Benefits compound quickly.

---

# Starting Off Remote

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/starting-off-remote
- **Tags**: remote, workforce, teamwork, culture, async

Starting a new job can be incredibly daunting in the most traditional of settings, and many companies are set up to onboard new in office employees. As the trend towards remote continues to gain popularity, hiring new employees and starting new jobs have a whole new set of challenges.

### For Employers

What does onboarding look like for a remote position? Laptops and office supplies show up at the front door instead of being delivered to a crowded floor of cubicles. Onboarding materials disseminated through HR zoom calls instead of in empty conference room tables. Virtual onboarding, when done well, can be an engaging and cost saving endeavor that empowers companies to widen their hiring pool and thereby attracting the best candidates without having to worry about when they can be on site for orientation…and how much it will cost to get them there. When onboarding remote employees, here are a few things to bear in mind.

#### Home Office set up 

When a new employee starts in an office building, there are always overhead costs. Consider offering home office setups to remote employees. If this is the employee’s first time working in a remote engagement model, they may need things like an external monitor, a comfortable chair, standing desk, and so on. Providing these things as part of the onboarding process is a great way to engage with a new remote worker and to send the message that they are valued. If new desks and fancy workstations are not in the budget, something as simple as company swag and a headset, or pens and post-its can go a long way in creating an inclusive work place even across state lines.

#### Team Introductions

Have a formal plan for welcoming new remote team members. If the remote employee is the only remote worker on the team, be mindful of how being the only person not in the room can feel. Limit side conversations as those can be impossible to follow as a remote participant. If the rest of the team is also remote or there is a hybrid model, you are likely well practiced at video conferencing etiquette, but be sure to be mindful that the new teammate isn’t familiar with team norms just yet, and those can be really difficult to convey virtually.

#### Intentional Engagement Model

After intros have happened, don’t forget that your new remote employee is not randomly meeting people at the coffee bar in the office kitchen. Be thoughtful about how your new worker will engage with people on the team and across the company. Setting up onboarding meet and greets, daily checkins or regular team meetings are a great way to help your new employee get to know the culture of the company. Don’t hesitate to sprinkle in a few lighter, more social opportunities to get to know one another virtually as well. There are myriad opportunities for virtual team building, do your research and have a plan.

#### Lean in to Async

Use asynchronous chat tools as a way to build company culture across time zones and work schedules in the absence of a shared physical location. Fun channels that are specifically for employees to interact on a more personal level are a great way to help connections form. This may take some support from a few motivated participants to get off the ground, but play around with the model to fit your team’s needs. Here are some ideas to get you started:

### For Employees

When starting off as a remote worker at a new company, or when working at home full time for the first time, you may face some new challenges. Hopefully your employer has some infrastructure established to support you in your new adventure. If not, you can absolutely take some steps on your own to ease the transition. Additionally, a lack of intentional engagement models with remote employees may mean an opportunitiy for you to be a change agent in that space!  Either way, here are a list of tips that you may find helpful as you start off remote!

#### Schedule time with your team

It can be easy to fade into the background as a remote employee, especially if you are in a hybrid or mostly non-remote setting. Try to be as proactive as you can and schedule 1:1 time with your teammates. It can be helpful to have a bit of a structure for these one on one get to know you calls, but try to keep things light in the beginning. These are a nice place to share your elevator pitch of your career path that led you to being on this team. Additionally, it is a great forum to share a hobby or two you have or an interesting fact about yourself. It would also be appropriate to have a question or two about each person’s role, their favorite part about working on the team and, especially if they are remote also, any tips they have about being a good teammate. The goal here is to open the lines of communication. 

#### Designate a work space

Home may be where the heart is, but it’s also where a LOT of distractions reside as well. Depending on your space situation, dedicating a whole room as an office may not be an option. That doesn’t mean remote work is not an option for you! Having a space where you work in your home is a great way to keep the lines drawn between home and work. 

#### Keep a schedule

Obviously the flexibility of remote work may fly in the face of the need for a schedule, but try to establish some sort of routine for yourself. This will greatly facilitate a healthy work-life balance. Of course your routine may need to change for one reason or another, but maintaining some sort of start/stop time will help keep work from taking over your whole life. 

### When in doubt, Take a Beat

Whether an employee or an employer, remote work affords a great deal of flexibility and freedom. There are some barriers to overcome (just as there are in an office setting), but empathy for one other is a great foot upon which to start. Whether a brick and mortar or a remote teammate, employee or employer, take a beat and consider one another’s perspective. Remote work is here to stay, and the more we can all consider its impact on one another and take steps to craft an environment of equity and inclusivity, the easier its adoption will be for all.   

---

# Taking the Leap

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/taking-the-leap
- **Tags**: career, culture, growth


## My First Career 

Ten years ago, I went to a college orientation and decided what I wanted to do for the rest of my life blindly. I chose what looked fun, challenging, and also, a little glamorous. Nursing appealed to me because, on paper, it looked like a career that would position me to:  
- help my community
- save lives
- have a “recognizable” career title and path
While most of this was true, not all of that translated to my actual experience. After five years of being a nurse, what I found was I had a career that gave me an opportunity to: 
- form a countless amount of relationships with patients and colleagues
- use critical thinking every minute of the day
- build trust in my instincts and decision making
This was all great, but the real life experience fell short of what I was anticipating it to be. I didn’t feel fulfilled, and at six months, I knew nursing wasn’t the career for me, but I knew there was still a lot to learn in nursing and being an “adult” with a career. I worked my way from a “new grad” nurse to a preceptor for new nurses and up to charge nurse. The growth I gained was invaluable. I learned leadership skills, communication, and working environments that I do and don’t want to be in. I also got my Master’s Degree in Health Informatics which started to open up the universe of careers and made me think that it may be time to move on. 

## Looking for Change

I knew going into a career search that I would need to leverage many of my skills that I gained as a nurse. All of these skills were transferrable, but how was I supposed to tell that story?
For me, networking was the game-changer. I began by simply talking about my desire to change my career with friends and family. My answer to “How’s work?” changed from, “it’s great” to “I’m thinking I need a change”. These conversations were an open door to talk to others about my desires, concerns, wants, and needs. A simple, “I’m thinking about leaving my job,” or “I’m looking to make a career change,” sparked conversations that I never could have planned. One of these such conversations presented an opportunity in the technical consulting world, and I couldn’t turn it down. 
I started slow and began as a contractor in a software consulting firm while maintaining my nursing job. I began forming a foundation, and trying out the career prior to working full time. I got my Scrum Master Certification, started learning how to code, and dipped my toes into the world of product development.  
It almost felt surreal. The culture was better than anything I had ever experienced, the work had a huge learning curve, and the schedule was vastly different. Those first few months involved a lot of information overload and processing, but as time passed, I started feeling more confident in this new world. Small wins kept me motivated and on track. I started to understand the conversations happening around me and began to contribute more in meetings because I had important and relevant things to say. One day I woke up and knew I was ready to fully commit. 

## A New Chapter

After the brief contracting period, I started full-time. I jumped in head first, and immersed myself in my new career. My onboarding was a deep dive into every aspect of the firm. I worked on web app development, brushed up on the Agile philosophy and frameworks. I learned about UX, design, and the beginnings of creating a product. Every time I had an opportunity to learn something new, I partnered with a coworker for a foundation and then expanded my knowledge through videos, tutorials, and readings on my own. I became a sponge and soaked up all the information I could. The goal of any consultant is to be fully billable, and I pursued that goal with all my energy. 
When I started my first contract with a client as part of an Agile transformation, I was ready. My education in agile and software development combined with my skills from nursing positioned me to excel in the world of client-facing work. 

## One Year Mark

Making this decision was life-changing and nerve-racking. I was unsure about many things: how this would affect my day to day, would the work be enjoyable, and how would I learn everything? Luckily, with help from my coworkers, it has been a transition that I would never take back. I feel supported and have found a safe environment for me to continue my growth. Now that I am a year in, I am full of reflection and want to share some things I have picked up along the way. 

### Be comfortable with the uncomfortable

When you are starting a new chapter, there is going to be a WHOLE lot of newness. Getting yourself ready to be comfortable in those unfamiliar spaces will really prep you for what’s to come. Here’s what that looks like:
- Soak up all the information and context you possibly can
- Show progress and never stop learning
- Take on work that challenges you or makes you uncomfortable and learn from it

### Trust my instincts

Remember that while this chapter may be new, you aren’t on the first page of your story. By this point, you have likely amassed many different experiences and solid instincts. Trust them as much as you can. Here are some ways you can do that:
- Produce work that you are proud of and iterate on that work to reach the expected outcome
- Don’t struggle in silence; ask for help when you are unsure
- Contribute to meetings; you DO have previous experience to draw from

### Gain independence, build confidence

Each day in this new space, you will learn things. As you learn them they become part of what will make you independent. Lean on that and allow those experiences to build your confidence level in the “new”. Here are some ways to go about that early on:
- Know what resources are available to you and credible to use
- With each task and piece of work produced independently, you will begin to notice your strengths and ways you can contribute to the team
- Use the positive feedback to fuel you, and negative feedback to help guide you in the right direction

## Reflection

Before changing careers, I did my research. I took time to consider all of my options. While taking the leap is the hardest part (it is uncertain and scary) it is also exciting. My leap is one of the proudest moments of my twenties. I knew I needed a change, and I had the courage and drive to make it happen.
Now: I couldn’t be happier. Going into this chapter was almost easier than starting my first career because I wasn’t starting from scratch. I am choosing my own direction. I learn about topics that interest me, and I push myself out of my comfort zone in more ways than one. I continue to learn about the software industry and Agile coaching while working with some of the best. A year ago, I never would have thought this is where I would be, but now that I am here, I can’t imagine it any other way.

---

# The Message Void: Managing Notifications

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/the-message-void-managing-notifications
- **Tags**: culture, remote, async, communication, collaboration, conflict


### Keep the dishes clean with these helpful tips

This article helps readers understand the benefits of good personal inbox hygiene, as well as actionable steps to help them stay on top of incoming messages. This helps reveal system-level causes of message overload, but we do not explore the practices and procedures to stop those leaks at the source in this article.
Properly managed communication channels help employees avoid stress and burnout while staying productive during focus times. Employees, both remote and in-person, may be faced with a barrage of messages that, if left without a filter, make it almost impossible to focus for any extended period of time.

### Mitigate Message Distractions

Messages are a big slice of the communication pie. Teams working across the world, across the city, or across the room message back and forth in direct messages, channels, and across various mediums. Messaging is awesome. It helps everyone stay on track and abreast of developments on pertinent projects. The problem arises as volume increases. Groups with two co-workers, three co-workers, your whole team, and certain employees from other teams. External groups, internal groups…the list goes on and on.
Almost everyone’s been added to a message channel where they aren’t needed. These channels are good places to start. Something as simple as turning off notifications from channels where you don’t need a ping every time a message is sent. Many message services offer a middle ground where you get notified when someone mentions you by name but silences other messages.
There are messages you want to read the moment you get them. Messages from your boss or team on current projects might change your daily plan, and they should be few and far between. There are also messages you don’t need to reply to right away. Depending on your profession, these can come in all shapes and sizes.

### Set Aside Time for Messages

If you’re feeling overwhelmed by your current message flow, we recommend blocking off parts of your day where you focus one hundred percent on replying to messages, emails, and other correspondence. You can peruse channels you’ve silenced and catch up on what’s happening. It's a nice way to stay in the know while lessening total daily notifications. If someone needs your assistance, they can reach you directly.
No size fits all, here! A deeper dive into your team and company’s messaging habits will give you the info you need to figure out whether you are okay responding to messages as they arrive during the day, or if you can increase your focus by going through all your unread messages with less frequency. This could be every hour, every day, or even every week! 
A constant flow of messages is one common source of frustration at work. Spending a little time auditing problems at work can output tremendous value, and there are implementable solutions for the symptoms as well as the cause of these frustrations. Silencing or deprioritizing a few channels will help you, but you can also dive deeper into why so many messages fly around.

### Need Some Help? 

We’ve got you! Small, incremental changes let you see results with a much clearer eye, often resulting in less ruffled feathers along the way. If you ever want to chat with people who know a few things about improving your work satisfaction, drop us a line! We are always happy to hear from you.

---

# The Price of Leaving

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/the-price-of-leaving
- **Tags**: career, culture, growth, workforce


### The Price of Leaving: Weighing the Costs of Switching Jobs

Dreaming of a better job with less stress, more purpose, and a bigger paycheck is easy, but finding that dream is not. It is natural for employees to wonder if there is a better role for them waiting in the wings. When it comes time to look at new positions, it’s important to consider the time, money, and energy it takes to find a new job. This post will examine some of those considerations, and ensure an intentional approach to planning the path forward. 

### The Gilded Cage: What Jobs Give (and Take)

People need jobs. A paycheck covers expenses, health insurance covers doctor visits, and retirement plans help you save for the future. These are tough to walk away from. Yet, switching jobs takes effort that adds up fast. Scouring listings, polishing resumes, and prepping for interviews, all while keeping up with your current gig, eats up hours and money. A 2023 Joblist survey highlights employee burnout: “Half of all workers report that they are experiencing burnout right now. The most common reasons cited by workers for their burnout are a lack of recognition by their employer (46%), limited growth opportunities at work (46%), and a toxic work environment (41%).” Burnout, in this case, makes it harder to put out good work and harder to expend additional effort looking for a new job. 
Even for those burnt-out employees, job perks make it more difficult to start looking for a new job. 
The State of the Global Workplace: 2024 Report by Gallup notes, “Gallup estimates that low employee engagement costs the global economy $8.9 trillion, or 9% of global GDP” (p. 3), linking disengagement to job dissatisfaction that reduces productivity. The report also highlights that 54% of actively disengaged workers “say they experienced a lot of stress the previous day” (p. 11), showing how staying in an unfulfilling job can spill into life outside work.  Without boundaries, such as ignoring work emails after hours, that frustration can dull family time, hobbies, and relaxation.
The trick is spotting the trade-off. Every job demands something: time, creativity, and patience for its rewards. A big corporate role might mean long hours, and a scrappy startup could bring constant flux. It’s important to figure out what you’re looking for. Certain people thrive in the startup flux, while others want something more structured. Before you wrestle with switching jobs, weigh what your role takes against what it gives. 

### The Fear of Change: Why Leaving Feels Like a Leap

Venturing into an unfamiliar career path sparks apprehension, even when job dissatisfaction drives employees to consider leaving. A shift to a new role disrupts routines, work relationships, and demands significant effort, from updating resumes to navigating interviews. The 2022 Journal of Vocational Behavior study on occupational regret reveals that “70% of workers who thought about quitting ultimately stayed, with fear of regret being the top reason.” This highlights how the fear of irreversible mistakes anchors employees in unfulfilling jobs. This fear, tied to job dissatisfaction, amplifies the perceived costs of a career change, as individuals weigh losing stability against uncertain gains.
This apprehension signals a need for reflection, not paralysis. Employees can explore adjustments within their current roles, such as taking on new projects, assuming additional responsibilities, or requesting internal transfers, to alleviate job dissatisfaction. For some, switching jobs or careers is the fresh start they need. Consider Mark, a manager who, feeling trapped, launched a mentorship program that rekindled his passion and boosted his team's morale. Conversely, Priya, feeling adrift in her current career, left tech for a nonprofit. Both confronted job dissatisfaction and took deliberate action.
Navigating this is a serious challenge. Colleagues, mentors, or counselors can help employees pinpoint the root of frustration, whether it’s a difficult manager, repetitive tasks, or misaligned values. This Journal of Vocational Behavior study notes, “Occupational regret is lived out daily as individuals labor in occupations they wish they had never entered” (p. 1), emphasizing the chronic toll of staying in roles that are misaligned. Employees can start by listing frustrations—identifying who, what, where, when, and why—to uncover patterns. If “Why” points to boredom, maybe a new task or a side project can ease job dissatisfaction without the full leap of switching jobs.

### The Bigger Picture: Balancing Risk and Reward

The career change costs are more than time and money. They’re about where you’re headed. Lingering in an "okay" role might be the easier choice, but not the right choice. That being said, switching jobs can also be the “easier, but not right,” choice. Employees who are too quick to jump from one job to the next assume that there’s no way for their current job to improve. Managers feel this, too: Losing people shakes teams, racks up training bills up to half an employee’s salary per SHRM, and frays the culture they’re building.
Before switching jobs, ask: What do I want work to be? Maybe it’s less about fleeing job dissatisfaction and chasing purpose and freedom. Managers can help by listening and assisting employees to shift daily work to better align with what they are looking for.  One common action is implementing “stay interviews,” which ask what keeps people around and what might push them out. It’s not about trapping people; it’s crafting a place they don’t want to leave.

### Conclusion: Choosing Your Path with Confidence

Switching jobs is a big move, like jumping from one train to the next. The career change costs time, money, stability, and more. It is almost impossible to know what the right way forward is, which is why taking time to reflect is so important. Whether you’re an employee restless for change or a manager bolstering team morale, it is important to take the reins. What’s your job giving? Taking? What’s at stake if you go? What kind of plan can you come up with to make switching easier, and does that change your answer?
There’s no one-size-fits-all answer, but there’s strength in stepping back. Talk it through with someone you trust. Jot down what’s bugging you. Managers, ask your team what they need to do their best. At En Dash, we live for this, delivering insights and tools to make work feel better, from taming turnover to lifting spirits. Ready to rethink your workplace? Let’s talk.

---

# What the Hell is an En Dash?

- **Type**: Blog
- **URL**: https://endash.us/blog/posts/what-is-an-en-dash
- **Tags**: health, goals, collaboration, teamwork, communication, culture


### Why We’re Called en dash

When people first hear the name of our company, they often ask: “What the hell is an en dash?:”
Most people know a period ends a sentence, a comma gives you a pause, and an ellipsis adds a little drama… But what about the en dash (–)? It’s a subtle mark, often overlooked, yet it carries a powerful meaning. We chose it as our name because it perfectly represents how we see work, progress, and transformation.

### The En Dash Itself

Unlike a hyphen (-), which ties words tightly together, or an em dash (—), which adds emphasis or expansion, the en dash is all about connection. It shows a relationship, a span, a bridge:
- 2010–2020 (a range of years)
- The Boston–New York train (a journey between two places)
(After the practical details — en dash vs. em dash vs. hyphen, and how to actually type one on any keyboard? We made a proper reference page: What is an en dash?)
The beauty of the en dash lies in the space it represents: a middle ground, a transition. That is the space where growth happens. We’ve built our model around this philosophy: creating environments where dialogue is open, where teams experiment safely, and where leaders guide with vision and empathy.  
It is in that space between that we can partner with individuals, teams and organizations to make work feel better. As this change takes root, the benefits extend beyond morale—teams deliver with greater focus, leaders make clearer decisions, and businesses see measurable improvements: faster time-to-market for new products, reduced operating costs through streamlined processes, and higher customer satisfaction scores.

### Why It Resonates With Us

For us, the en dash isn’t just a clever name—it’s our philosophy. We sit in the middle, helping connect leaders, teams, and strategies. We hold the space where dialogue can happen. We help people take the step between where they are now and where they want to be.
Real and lasting change happens in the middle—the messy, human, in-between space where people are moving from one way of working toward another. 
That’s where leaders gain alignment on strategic priorities, teams reduce wasted effort by working on the right things, and organizations see productivity rise without burning people out.
That’s what the en dash represents. We live in the space between and work to move the needle. Here are some examples. 

#### Silos – Collaboration

By moving from silos into a more collaborative model teams are able to accelerate cross-functional delivery by months instead of quarters.

#### Confusion – Clarity

Creating an atmosphere that honestly and directly deals with confusion and miscommunication creates clarity and shared understanding so leaders invest confidently in the initiatives with the highest ROI.

#### Good Enough – Better

Challenging that which has always been “good enough” moves organization to strive for better from driving continuous improvement that compounds into long-term gains.
Critically, this process is not about erasing what came before. It’s about helping professionals, teams or companies bridge the gap and navigate the way forward, moving them to a place where work feels better and therefore is better.

### The Power of the Dash

This tiny piece of punctuation holds the weight of what we constantly try to do: create connections, bridge gaps, and make the space between two points meaningful. And just like the en dash itself, it’s subtle. You don’t always notice it at first, but once you understand what it’s doing, you can’t imagine the sentence (or the business) working without it.
So that’s why we’re called en dash. Not because of grammar, but because the work we do is about the dash itself: the connection, the journey, the movement from here to there. And along the way, companies don’t just feel better—they become stronger, more adaptive, and better positioned to grow in competitive markets. 
Interested in getting some help in your work, to be more collaborative, efficient, effective and value-driven, while always ensuring people are at the core of any change?  Check out some resources we've created and use in our work, that can help you in your journey in our growing Toolkit.

---

# A Sample of Our Values Based Consulting Book

- **Type**: FieldGuide
- **URL**: https://endash.us/toolkit/items/values-based-consulting-book-lets
- **Tags**: management, career, culture, communication, teamwork, conflict, collaboration, agile, product, growth, prompts, governance, compliance, pmo, vmo, continuousimprovement, leadership, outcomes, alignment, planning, dependency

---

# Data-Ready Prompting: Input Formats and AI Context Setup

- **Type**: FieldGuide
- **URL**: https://endash.us/toolkit/items/genai-input-formats-context-prompting-better-practices
- **Tags**: ai, prompts

---

# GenAI Prompting Essentials for Lean Portfolio Management (for PMOs, APMOs and VMOs)

- **Type**: FieldGuide
- **URL**: https://endash.us/toolkit/items/lean-portfolio-genai-booklet
- **Tags**: ai, lpm, portfolio, scaling, product, prompts, project, projectmanagement

---

# KPIs, OKRs, Goals and Alignment Support with GenAI

- **Type**: FieldGuide
- **URL**: https://endash.us/toolkit/items/genai-support-okrs-kpis-goals
- **Tags**: kpi, workforce, goals, outcomes, alignment, scaling, pmo, vmo, agile, portfolio, project, projectmanagement

---

# Prompting Essentials for Agile Professionals

- **Type**: FieldGuide
- **URL**: https://endash.us/toolkit/items/general-prompting-guidance-essentials-genai
- **Tags**: ai, prompts

---

# A Beginner’s Guide to Understanding AI and Cognitive Biases

- **Type**: Handout
- **URL**: https://endash.us/toolkit/items/genai-beginners-guide-to-understanding-cognitive-biases
- **Tags**: ai, culture, antipatterns, dependency, health

---

# AI Enhanced Career Management for Project and Portfolio Managers

- **Type**: Handout
- **URL**: https://endash.us/toolkit/items/AI-enhanced-career-management-for-professional-project-managers
- **Tags**: ai, career, culture, guide, prompts, growth

---

# PMI Northern Nevada PDD Special Edition - Getting Started With AI Governance

- **Type**: Handout
- **URL**: https://endash.us/toolkit/items/pmi-nnv-pdd-getting-started-with-ai-governance
- **Tags**: ai, governance, portfolio, project, projectmanagement

---

# PMI Northern Nevada PDD Special Edition - The Product Dance

- **Type**: Handout
- **URL**: https://endash.us/toolkit/items/pmi-nnv-pdd-the-product-dance
- **Tags**: culture, communication, teamwork, collaboration, product, project, projectmanagement, design

---

# Top 40 GenAI Prompts for Project and Program Managers and PMO Leaders

- **Type**: Handout
- **URL**: https://endash.us/toolkit/items/genai-for-project-program-pmo-management-professionals-booklet

---

# Agile + Product + Tech for AI-Enabled Delivery

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/ai-agile-dev-scroll
- **Tags**: product, agile, development, kaizen, continuousimprovement, collaboration, delivery

Skip to main content Intro Thesis Assessment Three Forces The Opportunity Three Practices Principles Manifesto Start Now ☀︎ Light Agile & AI — A Scroll for Product & Engineering Teams
## Your team. Your process. The AI era.
How to evolve your agile practice, your developer experience, and your team rituals to make the most of what AI now makes possible together.
Read on Agile Workflows — Developer Experience — AI-Powered Development — Definition of Done — Continuous Improvement — Inspect & Adapt — Human + AI Craft — Agile Workflows — Developer Experience — AI-Powered Development — Definition of Done — Continuous Improvement — Inspect & Adapt — Human + AI Craft — The Core Idea You need agility to evolve your developer experience. And you need to evolve your DX to truly leverage AI in your digital builds. These aren't separate initiatives — they're one living system. When your process, your tooling, and your team rituals grow together, your capacity to do great work with AI grows with them. The teams thriving right now aren't the ones with the most AI subscriptions. They're the ones who've made continuous learning a core habit.
Where Are You on the Journey?
### Three questions. No wrong answers.
Work Tracking Does your team capture how AI was used on each ticket — the prompt, the tool, what worked? Yes Not yet Refinement Cadence Do you use refinement sessions to do AI-assisted pre-work before tickets enter a sprint? Yes Not yet Definition of Done Does your Definition of Done require AI-generated documentation with a human review sign-off? Yes Not yet The Foundation
### Three forces. One system.
01 — Practice
#### Agile as a Discipline
Agile at its best is a permission structure — an invitation to inspect how you work and make it better. That spirit is exactly what lets teams absorb new tools, learn from experiments, and grow every sprint. It's not just a process. It's a practice.
Without it ↓ Static team Same sprint structure for 3 years. Retros that produce no process changes. AI tools adopted ad-hoc, unevenly, with no shared learning.
Agile team Every retro has an AI segment. Processes update to match new capabilities. Prompt libraries grow. The team compounds its edge every sprint.
02 — Mindset
#### Product Thinking
When engineers think like product owners — anchoring every decision to user impact and real value — AI becomes a lever for outcomes rather than a novelty. The best work happens when the whole team is asking "what should we build?" alongside "how do we build it?"
Without it ↓ Without product thinking AI is used to generate clever code faster. Velocity increases. But the wrong things get built faster — and still don't move the metrics.
With product thinking AI helps with discovery, not just delivery. Teams ask "what should we build?" as much as "how do we build it?" Speed is applied to the right problems.
03 — Enabler
#### Developer Experience
Great developer experience is the soil that everything else grows in. Fast feedback loops, clear conventions, and frictionless tooling don't just help developers — they make AI suggestions easier to validate, integrate, and build on. Invest in DX and your AI investment multiplies.
Without it ↓ Poor DX Slow CI, inconsistent environments, unclear conventions. AI suggestions are harder to validate and integrate. Developers spend their saved AI time fighting the toolchain.
Great DX Fast feedback loops mean AI-generated code gets validated in seconds. Clear conventions mean AI suggestions fit the codebase naturally. The multiplier multiplies.
The Opportunity
### Agility is what unlocks everything AI can offer.
AI tooling evolves on a weekly cadence. Model capabilities shift. Best practices get rewritten. The good news is that agile teams are already built for exactly this kind of change.
The deeper gift of agile has always been its permission structure — the standing invitation to look at how you work and make it better. That invitation is more valuable than ever now. It's what lets your team experiment with new tools, learn from them, and build those learnings into how you operate.
Teams with a genuine inspect-and-adapt habit don't just absorb change. They get better because of it.
Click any node to explore the cycle The agile loop is not a metaphor. Each stage is a place where AI changes the work — if you let it. What to Try
### Three practical changes. Any one of them counts.
Not theory. Not a roadmap item for next quarter. These are things you can bring up in your next planning session and have running before the sprint ends.
01 Work Tracking Change to your work-tracking system
#### Add an AI field to every ticket.
A simple field on every story or task — for the starting prompt, the tool used, what worked, what didn't. It doesn't take long to fill in, but over time it becomes something genuinely valuable: your team's shared memory of how AI actually shows up in your work.
When that knowledge is captured, your team can learn from it together. Which prompts are worth reusing? Which tools saved the most time? Where did the model go confidently wrong? Shared learning compounds. Invisible learning disappears.
Works today in Jira, Linear, Azure DevOps, or any tracker with custom fields. You can add this field before your next standup. Linear — Issue Detail ENG &rsaquo; Sprint 24 &rsaquo; ENG-4471 Allow social login on the /register route Assignee M. Reyes Status In Progress Sprint Sprint 24 — Oct 14 Estimate 3 pts Starting Dev Prompt You Human decision: what context does this developer need? You've read the ticket. You know the codebase. Now write the prompt that tells your developer exactly where to start — which file, which pattern, which constraints. Then capture it. → + Add Starting Dev Prompt This field doesn't exist yet — but it should. 02 Ceremony Cadence Change to your meeting cadences
#### Double your refinements. Use them for collaborative AI pre-work.
Refinement sessions have always been where a team makes vague things concrete. Now they can also be where you bring AI in as a collaborator — before anyone writes a single line of code. Use the extra sessions to explore tickets together with AI assistance: draft acceptance criteria, surface edge cases, sketch the technical approach.
Developers who arrive at their keyboards with direction and context do their best work. Refinement is how you give them that.
Try proposing one additional refinement per sprint, framed as collaborative AI pre-work. See what changes in sprint predictability within a month. Refinement Session — ENG-4488 ENG-4488 — Feature Implement dark mode toggle No estimate — Backlog User can switch between light and dark themes. Preference should persist. You Human insight: what does this ticket actually need? You know the product context, the user need, and the technical landscape. Before AI can help refine this ticket well, your team brings that knowledge to the session. That's the thinking that happens before you click. → Run AI Pre-work A vague ticket. See what AI surfaces when you bring it into refinement. Acceptance Criteria User can toggle dark/light mode from the top nav on any page Preference persists in localStorage across sessions System preference ( prefers-color-scheme ) is respected on first load All existing components respond to the theme variable without component-level overrides Edge Cases to Consider User has no system preference set — default to light Pages containing embedded iframes or third-party widgets (charts, maps) may not inherit the theme Print styles should remain light regardless of preference Implementation Note CSS custom properties approach recommended over class toggling for breadth of coverage. If on Next.js, consider next-themes to avoid flash-of-incorrect-theme on SSR. 03 Definition of Done Change to your Definition of Done
#### Let AI draft the docs. Let humans make them trustworthy.
Expand your Definition of Done to include AI-generated documentation — inline docs, READMEs, API references, architecture decision records. This is one of the highest-leverage things AI can do for your team: produce thorough, consistent documentation at a scale that simply wasn't practical before.
The human review step is what makes it reliable. AI drafts fast, but it can also be confidently wrong about details only your team knows. A quick review by someone who wasn't the author closes that gap — and produces docs that future developers can actually trust.
Add two criteria to your Definition of Done: AI docs updated, and human review confirmed. These work as a single gate, in sequence. Definition of Done — ENG-4471 Unit and integration tests passing Quality PR reviewed by a peer developer Process Acceptance criteria verified in staging Quality No console errors in production build Quality AI-generated documentation updated (inline docs, README, ADR if applicable) AI Criterion — New Human review of AI-generated docs signed off (not the author) AI Criterion — New You Human decision: what does "done" mean for your team? Your Definition of Done reflects your team's values and standards. Adding AI criteria is a deliberate choice — a signal that your team takes AI-generated work seriously enough to quality-gate it the same way you quality-gate everything else. → + Add AI Criteria to Definition of Done Mark as Done &rarr; Your current Definition of Done is missing something. The Mindset
### Principles behind the practice.
On Experimentation
##### Try it before you institutionalise it.
The best AI practices emerge from genuine exploration, not top-down policy. Give your team space to experiment freely — then codify what genuinely helps. Systematising before exploring produces rules that nobody understands and everyone works around.
On Partnership
##### AI is a collaborator. You're still the expert.
Think of AI as a tireless contributor — a first-draft machine, a research partner, a rubber duck that never gets tired. It handles volume and breadth beautifully. Architecture, ethics, and user empathy are yours. The two together produce something neither can alone.
On Learning
##### Make your learnings visible to the whole team.
Reserve space in every retro for what AI taught you this sprint — what worked, what didn't, what surprised you. Unshared learning fades. Shared learning becomes part of how your team operates. The AI field on tickets is the start. The retro is where it compounds.
On Process
##### Your process is always a work in progress. That's the point.
Teams that feel empowered to propose changes — to their ceremonies, their Definition of Done, their workflows — find it much easier to absorb new capabilities as they emerge. You don't need permission to improve how you work. Agile already gives you that standing invitation.
On Tooling
##### Your DX choices are now a team decision, not a preference.
IDE plugins, AI assistants, local dev tooling — these compound across every developer-hour in your sprint. Choosing them thoughtfully, evaluating them together, and updating them intentionally is craft, not overhead.
On Quality
##### Human review isn't a bottleneck. It's the craft.
AI generates at a pace that can make review feel like friction. Reframe it: review is where your team's judgment, context, and care for users shows up. Speed without that care produces things fast. Speed with it produces things well.
The Spirit of It The teams doing the best work in the age of AI are the ones who kept their curiosity alive. They try things. They learn together. They keep getting better. Continuously improve your processes — in the true spirit of agile — so that your team is always exploring what's new, experimenting with what's promising, and building the best of it into how you work.
Ready When You Are
### Pick one thing. Try it this sprint.
The AI field. An extra refinement. An updated Definition of Done. Any one of these creates real momentum. You don't need to do all three at once — you just need to start somewhere, see what you learn, and go from there.
Connect with En Dash A Dev-Focused Scroll Your Team — The AI EraAgile — Product Thinking — Developer Experience — AI

---

# AI Delivery Friction Finder

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/ai-delivery-fiction-finder
- **Tags**: ai, collaboration, development, delivery, guide, agile

Skip to main content Start Finder Patterns Experiment Use it AI Delivery Friction Finder
## Find where delivery loses its shape.
AI does not fix the delivery system. It makes the delivery system easier to see: context gaps, late technical discovery, quality fog, flow drag, and broken learning loops.
Find the drag → Skip to the sprint experiment Remind me next week We'll email you the link now, plus one reminder next week. Set reminder This is not an AI maturity model.
It is a short working tool for a team conversation: where does work lose its shape between intent and delivery?
Rate ten friction prompts. Get a primary friction pattern and score breakdown. Download your answers as a markdown handoff. Two-minute diagnostic
### Read the statement. Rate the friction. Add the evidence.
Each card asks about one way delivery loses shape. The score is only useful if the team can point to a real example, so keep the evidence close to the rating.
Shared context keeps getting rebuilt. Where is your team on this? (1–5)
Not true for us Very true for us 12345 What makes you say that? Where did someone need background that should already have been in the work? Technical reality shows up after planning feels settled. Where is your team on this? (1–5)
Rarely true Constantly true 12345 What makes you say that? What did the team learn only after someone opened the codebase or dependency map? The team can produce work faster than it can prove the work is right. Where is your team on this? (1–5)
Clear evidence Mostly vibes 12345 What makes you say that? What evidence would convince a skeptical reviewer? AI increases local speed but makes system-level flow worse. Where is your team on this? (1–5)
Flow feels healthy Flow is dragging 12345 What makes you say that? Where does work wait, pile up, expand, or return for rework? Delivery signals do not change how the system works next time. Where is your team on this? (1–5)
Learning changes behavior Learning evaporates 12345 What makes you say that? What did the last sprint teach you that actually changed a working agreement? AI-generated artifacts are not grounded in a shared understanding. Where is your team on this? (1–5)
Grounded Detached 12345 What makes you say that? When AI drafts something, who can tell whether it reflects real intent and constraints? Dependencies, ownership, and constraints are under-described. Where is your team on this? (1–5)
Well understood Mostly unknown 12345 What makes you say that? What would make refinement more honest before the team commits? Acceptance criteria are hard to observe or test. Where is your team on this? (1–5)
Testable Ambiguous 12345 What makes you say that? Can someone prove the behavior works without reading minds? Work is too large to inspect quickly. Where is your team on this? (1–5)
Small and inspectable Too large 12345 What makes you say that? What is the smallest useful thing you could learn within three days? The team lacks a signal for whether AI improved delivery decisions. Where is your team on this? (1–5)
Signal is clear No signal 12345 What makes you say that? What would tell you AI helped beyond “we moved faster”? 0 of 10 rated Rate at least five prompts to get a useful result.
View result Reset Primary friction
### Context Gap
Your result will appear here.
What AI is exposing:
Team conversation:
Sprint experiment:
Use AI to Human check Signal Download markdown copy Email me my results: Send results Use the sprint planner The markdown file includes your ratings, notes, result, and freeform planner text.
The five patterns
### Most teams do not have an AI problem first.
They have a delivery-system problem that AI makes louder. The point is not to admire the diagnosis. The point is to pick the next constraint and work it.
01 · Context
#### People are rebuilding the same background.
Discovery, product intent, constraints, and codebase reality live in different places.
02 · Technical reality
#### The work looks ready until implementation starts.
Dependencies, ownership, tests, and architecture risks arrive too late.
03 · Quality
#### Correctness is harder to see than output.
AI can produce plausible work faster than the team can validate it.
04 · Flow
#### More work starts than can be inspected.
The team accelerates ticket movement but creates waiting, review piles, and rework.
05 · Learning
#### The system does not remember.
Delivery signals do not change refinement, working agreements, or the next experiment.
The takeaway artifact
### Turn the result into one sprint-sized experiment.
No transformation theater. No tool rollout disguised as improvement. One repeated friction. One change to the delivery system. One signal.
Step 1
#### Name the drag.
Where does work lose clarity, quality, or momentum?
Friction Where it shows up Step 2
#### Choose the experiment.
What will the team do differently for one sprint?
Small experiment Step 3
#### Define the signal.
What evidence will tell you whether the change helped?
Signal Step 4
#### Place the AI.
Will AI analyze, plan, execute, summarize, test, or inspect?
AI role Step 5
#### Place the humans.
What must people still judge, review, approve, or challenge?
Human check Step 6
#### Update the system.
If it works, what changes in your working agreement?
Working agreement update Use it with your team
### One result. One conversation. One experiment.
The score is a door, not a verdict. Here is the difference between leaving with a tools list and leaving with a system change — and three ways to run this with a real team.
The usual move
### “Go try AI.”
Problem Too broad to act on. Next step Tool browsing, prompt swapping, uneven adoption. Risk More output without a better delivery system. The better move
### “Find the drag.”
Problem Specific constraint in context, planning, quality, flow, or learning. Next step One team experiment in the next sprint. Signal Evidence that decisions, feedback, or quality improved. Use it solo first Run the diagnostic yourself before raising it with the team. Your own score is a draft agenda: the top friction is the conversation worth having.
Use it in a retrospective Have each person answer individually, compare friction patterns, then choose one shared system change for the next sprint.
Use it in refinement Run the scorecard against one upcoming story. If technical reality, acceptance criteria, or shared context are weak, improve the work before starting it.
The point
### Do not leave with a list of tools. Leave with one constraint to improve.
Run the Friction Finder with your team, then bring the result to refinement, retro, or sprint planning.
endash.us/toolkit/items/ai-delivery-fiction-finder Copy link En Dash Consulting
### Better decisions. Better flow. Better work.
AI-enabled delivery works best when agile leadership, product thinking, and software craft reinforce each other.
Explore the toolkit Talk with En Dash

---

# AI Governance for Professional Project Managers

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/ai-governance-basics-for-professional-project-managers
- **Tags**: ai, career, agile, pmo, vmo, delivery, continuousimprovement, project, projectmanagement

## AI Governance Isn't A New Discipline. It's Your Discipline Applied To New Risks.
For Project Management Professionals
### Why This Matters Now
63% Organizations lack clear AI accountability 40% Lower settlement costs with documented review 90 Days to implement basic governance 3 Places AI can show up in your projects AI failures rarely announce themselves. Most begin as productivity wins and reveal their impact only after decisions have been made, commitments delivered, or trust affected.
##### Federal Court Sanctions
Domain 1 Impact: Attorneys submitted legal filings containing nonexistent court cases generated by AI. The PM equivalent: a deliverable with fabricated references that looked legitimate.
PM Accountability: Could you defend this output if challenged? Was validation required before delivery?
##### AWS AI Agent Outage
Domain 2 Impact: AI coding agent with excessive permissions bypassed approval workflows, triggering configuration errors. The PM equivalent: team tools making changes without review gates.
PM Accountability: Do you know what AI tools your team is using? Are review mechanisms in place?
##### Retail AI Chatbot
Domain 3 Impact: Home-improvement retailer's AI gave instructions for electrical work requiring licensed professionals. The PM equivalent: product behavior creating liability exposure.
PM Accountability: Who owns the AI decision when it produces harmful guidance? Was this tested?
Project managers are on the front lines of accountability. This is not theoretical. This is happening now.
### The PM's Job Doesn't Change
AI doesn't create a new profession. It creates new risk categories inside the one already held.
##### Risk Management
Schedule, cost, resource, stakeholder risk. AI adds to this list. The Federal Trade Commission has made clear: businesses remain fully accountable for AI-assisted claims and representations.
##### Accountability
AI tools don't share responsibility. Responsibility follows existing roles. Documentation of human review reduced settlement severity by over 40% compared to cases with no review trail.
##### Governance
Projects are already governed. AI governance is the same discipline applied to new domains. It's everyday ownership of decisions, outputs, and consequences.
### Three Ways AI Affects Your Projects
AI doesn't require a new role. It requires understanding three distinct risk categories already familiar to PMs: deliverable accountability, team process oversight, and product quality assurance.
1
##### Domain 1: AI You Use
Your deliverables. Your signature. Your accountability. This is where most failures start. A status report drafted by AI. A client email that sounds polished. A risk summary that feels complete. The output looks finished, reads professionally, and arrives fast.
The Problem: AI doesn't generate verified content. It generates plausible content. When those two things look identical, the difference disappears.
PM Accountability Question: Can you defend this deliverable if challenged? What did you verify?
What This Means:
- Every draft is exactly that: a draft requiring validation
- Speed gains evaporate when errors reach clients or leadership
- The name on the deliverable owns the outcome, not the tool that created it
2
##### Domain 2: AI Your Team Uses
The tools in your delivery process, whether sanctioned or not. Code generation. Design mockups. Test automation. Data analysis. These tools are already embedded in workflows, often without formal approval or oversight.
The Problem: AI-generated work can introduce defects that pass initial review. A security vulnerability hidden in clean-looking code. IP concerns from training data sources. Automated actions that modify production systems without human checkpoints.
PM Accountability Question: Do you know what AI tools your team is using? Are review mechanisms in place?
What This Means:
- Cannot govern what cannot be seen—visibility comes first
- Review mechanisms must exist even when the PM isn't the reviewer
- Risk register must reflect AI-assisted delivery, not just project constraints
3
##### Domain 3: AI in the Product Being Built
When AI is the feature, not just the accelerator. This is where traditional PM assumptions break down. Testing strategies built for deterministic systems fail against probabilistic behavior. A model that works at launch may drift over time as data patterns shift.
The Problem: Same input doesn't guarantee same output. Edge cases multiply. Bias isn't always visible in testing. Post-launch monitoring becomes mandatory, not optional.
PM Accountability Question: Who owns the AI decision when it fails? Was accountability defined before launch?
What This Means:
- Testing must address probabilistic behavior, not just pass/fail scenarios
- Model drift and monitoring belong in handoff documentation from day one
- Accountability for AI-driven decisions must be defined before launch, not after incidents
### Domain 1: How AI Actually Fails
Generative AI rarely fails in dramatic ways. Most failures begin as productivity wins and reveal their impact only after decisions have been shaped, commitments made, or trust affected.
##### Hallucinations and Confident Error
NIST identifies this as a core risk: systems produce false or misleading information that appears credible. Confident and wrong is a known characteristic, not an edge case. Errors look like finished documents.
##### Context Misuse and Scope Drift
AI is applied beyond original intent. Output created for internal convenience becomes external-facing without review. Scope drift happens because reuse feels efficient.
##### Over-Reliance and Skill Atrophy
Stanford research shows people consistently overestimate reliability of fluent AI outputs. When AI output becomes the default, review gets lighter. Errors compound.
Every AI Output Is A Draft. The Name On The Deliverable Owns The Deliverable. The Tool Doesn't.
### Domain 2: AI Your Team Uses
##### Quality Risk
AI-generated code can introduce defects, vulnerabilities, and maintainability problems that look fine on first pass. The PM must ensure qualified review exists and is expected.
##### IP Risk
AI-generated work may incorporate training data material that's difficult to trace. Creates legal exposure, especially on projects with strict IP requirements or in regulated industries.
##### Security and Operational Risk
AI automation tools can execute actions and modify infrastructure. An unreviewed automated action can create real operational disruption. These are risk events, not just delivery problems.
##### Four Questions Every PM Should Be Able to Answer
- Where is AI being used in the delivery process?
- What review mechanisms exist for AI-generated artifacts?
- Is team AI use documented anywhere?
- Does leadership know the scope of AI use on this project?
These are not gotcha questions. They are basic project hygiene in 2026.
### Domain 3: AI in the Product
Where Traditional PM Assumptions Break Down
##### Testing Challenge
Traditional testing assumes deterministic behavior: same input, same output. AI is probabilistic. Outputs vary, edge cases multiply, behavior evolves. Testing strategy must reflect this reality.
##### Model Drift
AI models can degrade as the data environment shifts. A system that performs well at launch may behave differently six months later. Model drift belongs on the risk register.
##### Bias and Fairness
Training data carries historical biases. An AI system used for decisions can produce unfair outcomes even when no one intended that. The PM must ensure this is surfaced and governed.
##### PM Responsibilities for Domain 3
- Ensure testing strategies address probabilistic behavior, not just pass/fail deterministic checks
- Include model drift and post-release monitoring in the risk register and handoff documentation
- Ensure stakeholders understand what the system can and cannot do
- Define accountability for AI-assisted decisions before go-live
- Make post-deployment monitoring a planned deliverable, not an afterthought
### The Three Pillars of AI Governance
Three pillars address the three domains. Business Alignment ensures AI solves real problems. Data Discipline controls what goes in and out. Risk & Ethics ensures responsible outcomes.
##### Business Alignment
Connect AI use to measurable outcomes. Use case first, tool second. Reject AI where business purpose is unclear.
##### Data & Tool Discipline
Define data boundaries. Prohibit sensitive inputs. Standardize on approved tools. Default: AI outputs are inputs to human work.
##### Risk, Ethics & Adoption
Match oversight to impact. Define review steps before reliance. Permit escalation without penalty. Ensure responsible outcomes.
### 90-Day Governance Strategy
Small organizations succeed by treating governance as an everyday operating discipline, not a maturity model or transformation initiative. Start with real work.
1
##### Phase 1: Explore & Align (Days 0-30)
- Make current AI use visible across the organization
- Identify 3-5 candidate use cases rooted in actual workflows
- Evaluate across Business Value, Data Feasibility, Risk Exposure
- Assign named owner for overall AI use and outcomes
- Align early AI use to real business priorities
Done Looks Like:Named owner, approved use case list, one-page charter outlining scope and objectives, first-pass acceptable use policy, red-flag data zones documented
2
##### Phase 2: Design & Prototype (Days 31-60)
- Select priority AI use case to move forward
- Define success measures and guardrails
- Test small-scale prompts using low/no-code tools
- Design workflows, review points, and acceptable use
- Build lightweight, testable prototype with governance built in
Done Looks Like:Working prototype for one use case with logging, reviewer routing, stop-rules, and prompt QA/review loops established
3
##### Phase 3: Pilot & Evaluate (Days 61-90)
- Run controlled pilot with small group to gather real-world data
- Monitor outcomes, quality, and risk using qualitative and quantitative data
- Assess impact against targets, including unintended byproducts
- Capture lessons from real-world use
- Decide whether to scale, refine, or stop based on evidence
Done Looks Like:Evidence-based decision to expand, refine, or stop. Policies updated based on learnings. Review cadence and ownership set for ongoing operation.
### Four Things to Do Before End of Week
##### Start with visibility
- Ask the team this week: where is AI being used?
- Frame it as a planning conversation, not an audit
- Cannot govern what cannot be seen
- Start with use cases, not tools
##### Name one owner
- On every project, one person owns AI governance decisions
- In a small team, that's often the PM. Make it explicit.
- Assign ownership at both organization and use case level
- Same person may hold multiple roles, but functions must still exist
##### Create one use case charter
- One page: task, who's authorized, what data can be used, what review is required, who can stop it
- This is the unit of governance, not a policy manual
- Include purpose, scope, allowed/prohibited inputs, required review, known limitations, named owner
- This becomes the reference model for future use cases
##### Add AI risk to the register
- At minimum: accuracy risk, data exposure risk, model behavior risk if delivering an AI-enabled product
- Identify who could be harmed if output is wrong or biased
- Define where speed may conflict with accuracy or fairness
- Define clear stopping conditions and escalation triggers
- It's a real risk. Treat it like one.
#### Three Things Worth Remembering
Risk management discipline is the right foundation. AI doesn't require a new professional identity. It requires applying what's already known to new risk categories.
AI shows up in three places, and each demands a different governance response. Most failures begin as productivity wins.
A policy manual is not needed to start. One charter and one honest conversation with the team is needed.
### Learn More
For a comprehensive guide to AI governance implementation:
Getting Started with AI Governance: The Field Guide for Small Businesses by John Halberstadt and Steve Daniel En Dash Consulting, 2026 View on Amazon

---

# AI Governance Framework

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/scroll-our-ai-governance-framework
- **Tags**: ai, governance

Skip to content AI Governance Framework En Dash Scroll The GenAI Governance Field Guide
## AI Governance That Can Actually Be Used
A practical framework for bringing generative AI into real work with clarity, restraint, and measurable progress — before convenience turns into unmanaged risk.
Why this starts here
### AI is already inside the work.
Governance begins the moment AI influences judgment, communication, or decisions.
This framework is built for organizations that do not have the luxury of massive compliance teams, custom model stacks, or years to prepare. It starts with a simpler truth: generative AI is already present in drafting, summarization, research, customer communication, and operational work.
The aim is not to slow useful work. It is to make responsibility visible, keep trust intact, and ensure adoption stays tied to real business value rather than tool momentum.
AI outputs enter real workflows without review Sensitive data slips into prompts unnoticed Fluent language looks finished long before it is safe Decisions get shaped by AI summaries no one verified The model
### Three pillars. One operating discipline.
The framework centers on three durable concerns — business alignment, data and tool discipline, and risk, ethics, and adoption control — that only work when they work together.
A use case that is aligned but poorly bounded still creates exposure. Convenience without data control normalizes risk. Adoption without oversight turns helpful output into silent dependency. The SVG below shows how these pillars support each other — and what happens when one is weak.
Operational controls
### Clear boundaries. Explicit review. Named ownership.
The most practical controls are not the heaviest ones — they are the ones people actually follow.
Red-flag data zones, plain-language acceptable-use rules, one-page use case charters, review steps scaled to impact, and the right to escalate when output feels wrong. A small number of explicit rules, repeated consistently, outperform long policy manuals that never shape day-to-day behavior.
Non-negotiable controls
- No credentials, privileged content, or uncontrolled confidential material in prompts
- Human review before any client-facing, employment, legal, financial, or safety-significant output
- Unambiguous authority to approve, pause, or stop any use case
The implementation arc
### Ninety days. Three phases. Evidence before scale.
Days 0–30
#### Explore and align
- Make existing AI use visible across real workflows
- Name a sponsor and a small taskforce with explicit decision rights
- Select a narrow portfolio of high-value, governable use cases
- Define red-flag data zones, quick rules, and early acceptable-use guidance
Days 31–60
#### Design and prototype
- Define success metrics before building anything more complex
- Test prompts and workflow steps using low or no-code patterns where possible
- Embed logging, prompt QA, review loops, and stop rules into the pilot path
- Prepare participants with clear communication, expectations, and escalation paths
Days 61–90
#### Pilot and evaluate
- Run the pilot in real work with measured outcomes and monitored exceptions
- Track value, quality, risk signals, and lessons learned under actual time pressure
- Update policies, controls, and review criteria based on evidence, not optimism
- Finish with a decision: expand, refine and rerun, or stop
The leadership layer
### The framework stays human.
Even as tools change, the durable parts of governance do not. Accountability remains human. Review remains necessary where consequences are material. Trust remains fragile, especially in small organizations where client relationships, reputation, and judgment are closely tied to individuals rather than buffers or brand distance.
That is why the framework treats measurement, transparency, training, escalation, and defensibility as part of normal leadership rather than as an afterthought. Governance is not a sidecar. It is the discipline that lets useful adoption continue without forfeiting control.
01 — Visible use Inventory how AI is already influencing drafting, analysis, communication, and decisions. Hidden use is unmanaged use.
02 — Accountable roles Map governance onto existing roles. In smaller organizations, part-time governance is normal. Ambiguous ownership is not.
03 — Ongoing review Use a practical cadence to revisit active use cases, boundary drift, tool sprawl, policy gaps, and emerging dependencies.
04 — Defensible practice Keep lightweight records of major decisions, approvals, exceptions, and lessons learned so the organization can explain what it knew, chose, and controlled.
Where the framework shows up Operations
#### Use cases before tool momentum
Start where recurring work is real, measurable, and bounded. Summaries, first-pass drafting, structured analysis, and internal knowledge flows can all be improved without pretending the tool is the strategy.
Data & Process
#### Safe inputs. Reviewable outputs.
The framework assumes ordinary constraints: limited staff, overlapping roles, embedded AI features, and incomplete technical infrastructure. That is why red-flag data zones, tool limits, and review steps matter so much.
Leadership
#### Scale only after evidence
Pilots are not proof because they exist. They become proof when outcomes, quality, and control can be observed under real use — and when leadership can still explain who owns what if something goes wrong.
Responsible AI adoption is not a race to the most automation. It is the practice of making useful progress without surrendering judgment.
En Dash – Make Work Feel Better

---

# Async Work

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/async-work-scroll
- **Tags**: async, communication, collaboration, teamwork, culture, remote, workforce, focus

Skip to main content Intro The Problem What is Async Principles Benefits Sync vs. Async Practice Mindset How to Start Dark Asynchronous Work
## Collaborate and Listen … Don’t Stop
How Async Collaboration Makes Work Feel Better
Let’s get into it Scroll The Problem
### Work is SO Chaotic
Work today is loud, constant, and interruptive. We are drowning. But the problem isn’t collaboration — it’s that we’ve made synchronous collaboration our default.
Burnout Shallow work Decision bottlenecks Unnecessary meetings “Urgency theater” No room to think creatively
#### Your Focus Time Calculator
Before you drag the slider — take a guess at how many meetings your team holds each week. Then see what that number is actually costing.
Meetings per week 10 — hours of productive time lost per week Focus time In meetings Context switching Assumes 45-min average meeting + 23-min context-switch recovery cost (Gloria Mark, UCI). Based on a 40-hour work week.
Let’s Define Our Terms
### What Async Actually Is
Async = communication that doesn’t require people to be present at the same time. That’s it. Full stop. It doesn’t mean you don’t collaborate — it means you collaborate on your own terms. Myth “Going async means you don’t collaborate.” Fact You collaborate more thoughtfully — with actual time to think before responding. Myth “Async means you never meet and work gets slower.” Fact Async can make teams faster. Meetings become shorter, sharper, and actually useful. Myth “Async means leaving people hanging.” Fact Clear norms and response-time expectations mean no one is guessing what’s happening. The Foundation
### Three Principles of Async
Master these three things and async will transform how your team works — and how work feels.
Clarity Visibility Respect 01 What tool to use — and exactly when to use it When meetings are truly necessary (less often than you think) Response time expectations — what’s normal vs. actually urgent How to signal urgency without causing unnecessary drama What “done” actually looks like for your team Who owns which decisions — no more circular conversations 02 Decisions get documented — not buried in someone’s memory Context is recorded so anyone can catch up without a meeting Artifacts people can review on their own schedule Work lives somewhere visible — not only in someone’s head Newcomers can onboard without interrogating teammates 03 Not expecting instant replies — let people do their best work first Protecting focus time — yours and everyone else’s Letting people breathe, think, and come back with something great Writing clearly so others don’t have to chase you for context Using channels instead of DMs so knowledge is shared, not hoarded Creating quiet hours — because some work needs silence Why It Works
### Async Helps Us
Unlock each benefit one at a time.
Think Instead of reacting in a meeting, team members contribute ideas in a shared doc the day before. Everyone gets time to process, research, and form thoughtful opinions — which means the live discussion is deeper and less chaotic. Focus Messages are written clearly with “respond when you can” expectations. People mute channels, batch replies, and get long uninterrupted blocks of time. Work moves forward without everyone needing to be online simultaneously. Include A decision doc is shared with all stakeholders — including quiet voices, remote folks, different time zones, and people who need more time to digest. Everyone weighs in before anything is finalized. Create Designers, PMs, and engineers collaborate in FigJam or Notion asynchronously — adding sketches, comments, and examples over several days. By the time they meet, they’re refining ideas, not inventing them from scratch under pressure. Breathe Because not everything is urgent and synchronous, people have margin. They can step away, take a walk, pick up a kid from school, and come back — without the work falling apart. Sustainable pace instead of frantic chaos. Unlock Next “Work does not have to feel chaotic… it can feel better.” En Dash Consulting Make a Call
### Sync or Async? You Decide.
Six real work scenarios. Before you click — pause and think: does this situation need real-time presence, or would thoughtful async serve the work better?
Question 1 of 6 0 / 6 Make It Real
### Put It in Practice
Check off what you’re ready to commit to. Start with one or two — small changes compound fast.
Messaging Meetings Workflows ✓ Write a clear topic line or first sentence so people know what they’re responding to ✓ Use threads — please, for the love of all that is holy ✓ Indicate urgency without drama — if it’s not on fire, say so explicitly ✓ Normalize “respond when you can” — and actually mean it ✓ Use Scheduled Send — your 10pm idea doesn’t need to be their 10pm anxiety ✓ Summarize decisions in the thread so no one asks “wait, what did we decide?” 0 / 6 ✓ Send artifacts — docs, decks, context — at least 24 hours before any meeting ✓ Start meetings with alignment, not information-dumping ✓ Make meetings smaller — only invite people who actually need to be there ✓ Share recordings with timestamp highlights so attendance can be optional ✓ Document decisions and owners immediately after every meeting — no exceptions 0 / 5 ✓ Status lives in a place, not a person — end “can you ping Jamie for an update?” ✓ Templatize — create reusable structures so handoffs are frictionless ✓ Set clear review cycles and deadlines — no ambiguity about when things are due ✓ Define clear handoffs: who does what, by when, and where it lives when done ✓ The litmus test: does work keep moving even when someone is out? If not — fix it. 0 / 5 The Real Shift
### Async is a Mindset
It’s not just tools or tactics. It’s letting go of urgency theater and building actual trust in your team.
“Everything must be immediate” → Thoughtful beats fast “I need your time right now” → “I need your clarity” “If you’re not online, you’re not working” → Trust the work, not the presence “A slow response means not caring” → A slow response means deep thinking “I need to be in every meeting” → “I’ll read the recap and add my thoughts” Start Today
### How to Start
Four steps to kick off your team’s async journey. Click each step when you’re ready to commit to it.
✓ 01 Team Norms Conversation Have an honest conversation about how you communicate now — and how you want to. The free En Dash Miro workshop is a great starting point. ✓ 02 Pick Starter Practices Choose two or three practices from the checklist above. Don’t boil the ocean — small changes compound fast. ✓ 03 Leverage Existing Tools You probably already have everything you need — Slack, Notion, Loom, your calendar. The goal is to use them differently. ✓ 04 Learn and Adjust Async is a practice, not a destination. Retro regularly and keep tuning what actually works for your team’s rhythm. En Dash Consulting “Work does not have to feel chaotic… it can feel better.” Read the Blog Chat with Caitlin An original Scroll, by En Dash

---

# Build a Dashboard with Claude

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/build-dashboard-claude-scroll
- **Tags**: ai, collaboration, prompts, guide, outcomes

Skip to main content
- Problem
- Workflow
- Builder
- Use Cases
- Patterns
Dark
- Problem
- Workflow
- Builder
- Use Cases
- Patterns
01 A Practical Guide — No Code Required
## Turn any report into a live client dashboard
Your clients don't need another PDF. They need something they can click, filter, and explore. With Claude or ChatGPT, you can build a bespoke interactive dashboard from an Excel file or PDF report using nothing but plain language.
See the workflow &rarr; 1 Prompt to get started ~5 min First version ready 0 Lines of code needed The Problem
### Static reports leave clients doing the work
You spend hours building a clean Excel workbook or polished PDF. You send it over. The client opens it, scrolls through it, and then emails you three questions that were already answered in the data — they just couldn't see it. Static deliverables are one-way. They don't let clients filter, explore, or ask their own questions.
An interactive dashboard changes that dynamic entirely. It puts the data in the client's hands in a way they can actually navigate. And building one no longer requires a developer, a BI tool subscription, or any technical skill on your end.
Static report — what you send today – Fixed view — one layout, one perspective – Client can't filter by date, matter, or category – Every new question means a new export from you – Key numbers are easy to miss in a wall of cells – Feels like a data dump, not a tailored deliverable Interactive dashboard — what this guide builds ✓ Client controls the view — clicks to filter and explore ✓ Charts update live with dropdowns and toggles ✓ One shareable file handles most follow-up questions ✓ Key figures are prominently surfaced and labeled ✓ Feels bespoke, built specifically for their situation The Workflow
### How to build a dashboard with Claude — four steps, start to finish
This is the complete process. It works with Claude — which is recommended for producing clean, self-contained HTML dashboards — or ChatGPT. Select each step below to see exactly what to do at that stage.
1 Prepare your data Clean and export your source file 2 Upload to Claude Attach the file directly in chat 3 Write your prompt Describe what to show 4 Iterate & share Refine in conversation, then export Interactive Tool
### Build your Claude dashboard prompt
Before typing anything into Claude, think through what your client actually needs to see and do. The selections below guide that thinking and assemble a ready-to-use prompt. Copy it directly into Claude alongside your uploaded file.
Prompt Builder — compose your first message to Claude 1. What are you uploading? Before selecting: what format is your source file, and how clean is the data?
Excel (.xlsx) CSV PDF report PDF with charts 2. What should the dashboard surface? Before selecting: what are the two or three numbers your client will actually care about?
Totals & KPIs Trends over time Category breakdowns Comparisons 3. What interactivity does the client need? Before selecting: will your client want to slice the data themselves, or just read the highlights?
Dropdown filter Summary headline row Sortable table Clickable charts 4. Who is the audience? Before selecting: how technical is your client? Should the dashboard explain itself, or just show the data?
Non-technical client Technical / expert Executive audience Needs narrative context Your generated prompt — copy into Claude alongside your file Make at least one selection above and your prompt will appear here. Copy prompt to clipboard Reset Use Cases
### What this looks like in practice
The pattern is the same across professions: upload your data, describe what you want the client to see, and let the AI generate the interface. Here's how it plays out in three common contexts.
01 Law Firm Matter cost breakdown for a client You have a monthly billing summary in Excel. Instead of a flat spreadsheet, you build a dashboard that lets the client filter costs by matter, attorney, or task type. A headline section shows total fees, outstanding balance, and hours billed this month. The client gets a self-service view without five follow-up calls to you.
02 Engineering Firm Project progress report for a developer You export milestone and budget data from your project management tool. The dashboard shows completion percentages per phase, flags anything over budget or behind schedule, and includes a sortable table of all line items. What used to be a 12-tab workbook becomes a single-page view the client checks weekly.
03 Financial Adviser Quarterly portfolio summary You pull account performance data into a CSV. The dashboard shows overall returns, allocation by asset class, and a time-series chart of portfolio value — with a dropdown to isolate any single account. A plain-English interpretation below each chart means you no longer need to write a separate commentary memo.
Pre-flight Checklist
### Before you hit send
Work through this list before uploading your file. Check each item off as you confirm it — the progress bar tracks your readiness.
Readiness checklist 0 of 6 complete ✓ My file has clear, descriptive column headers in the first row ✓ I have removed any footer summary rows that aren't raw data ✓ I know the two or three key figures my client cares most about ✓ I know whether the client will filter the data or just read the highlights ✓ I have removed any sensitive data not intended for the client ✓ If using a PDF: the file is text-based, not a scanned image Prompt Patterns
### Prompts that reliably work
These are proven prompt structures for common scenarios. Expand any item to see the full prompt text you can adapt and paste into Claude alongside your file.
Starting from scratch with an Excel or CSV file ⌄ Use this when you have raw data in Excel or CSV and want Claude to do the full job: parse the data, design the layout, and add interactivity. The more specific you are about what to show, the better the first version will be.
I've attached an Excel file containing [describe the data — e.g. monthly billing records by matter and attorney]. Create a single-page interactive HTML dashboard that shows: [list 2-3 things — e.g. total fees billed, a breakdown by matter, and average cost per attorney]. Include a dropdown filter so the user can select a specific [category — e.g. matter or month] and all charts update accordingly. Use plain-English labels throughout. Return the complete HTML file as a self-contained artifact. Extracting data from a PDF report ⌄ Claude can read text-based PDFs directly and extract numerical data from them. This is useful for board reports, published analyses, financial statements, or any structured document you receive from a third party.
I've attached a PDF report. Please extract all numerical data from it — any tables, figures, and key metrics mentioned in the text. Then build an interactive HTML dashboard that displays: [describe what you want shown]. Include a summary section at the top with the most important figures highlighted in large text, and charts below. Return the full HTML as a self-contained artifact I can open in a browser. Iterating on an existing dashboard ⌄ Once Claude has produced a first version in the conversation, you can refine it without starting over. Just describe the change you want in plain language. Claude edits the existing code rather than regenerating from scratch, so revisions are fast.
In the existing dashboard, please make these changes: 1) Change the bar chart on the left to a line chart showing the same data as a trend over time. 2) Add a "Total" figure in large bold text at the top of the page. 3) Change the chart fills to dark navy blue. Keep everything else the same and return the updated full HTML. Adding a written narrative alongside the charts ⌄ If your client needs context rather than just charts, you can ask Claude to write interpretive text directly into the dashboard — so it reads like a report and works like an app at the same time.
Below each chart in the dashboard, add a short paragraph (2-3 sentences) that explains in plain English what the data shows and what the key takeaway is. The tone should be professional but not stiff — write as though explaining findings to a senior client who is smart but not a data expert. Do not just describe what the chart shows. Interpret it. Refreshing the dashboard with new data next month ⌄ The dashboard you build this month becomes a reusable template. When the data refreshes, upload the new file with the same prompt and get an updated version in minutes. No rebuilding, no reformatting.
I've attached the updated Excel file for [next month / quarter]. It has the same column structure as before. Please rebuild the dashboard using this new data, keeping exactly the same layout, charts, filters, and interactivity from the previous version. Return the updated full HTML as a self-contained artifact. What's next Put it into practice with En Dash. The first dashboard won't be perfect. Send it, get feedback, and refine it in the same conversation. That iteration loop — not the prompting itself — is the actual skill. If you want help making it yours, we're here.
Explore our Governance Workshop &rarr; Soundboard with Steve &rarr;

---

# Claude and PowerBI

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/claude-powerbi-scroll
- **Tags**: ai, career, guide, prompts, development

Skip to main content
- Intro
- Conversations
- Patterns
- Tips
Claude &times; Power BI
## Five conversations that change how you work in Power BI
Most people use Claude like a search engine. Ask a question, get an answer, move on. That's the wrong model. Claude works best as a thinking partner — and once you learn to recognise which of five conversation types you need, everything gets faster.
Explain Build Debug Critique Strategize Start here
### Which conversation do you need right now?
Pick the scenario that matches where you are. We'll point you to the right conversation type — and jump you straight there.
"I keep seeing CALCULATE everywhere but I don't actually understand what it does."
→ Explain
"I need a rolling 13-week average that respects the slicer selection."
→ Build
"This measure worked in isolation but returns blank the moment I add a date filter."
→ Debug
"This report works, but my manager keeps saying it feels cluttered."
→ Critique
"My director wants a dashboard by Friday and I have no idea where to start."
→ Strategize
The framework
### The Five Conversations
Every productive Claude interaction in Power BI fits one of these five types. Click each part of the example prompt to see why it's there.
Explain Build Debug Critique Strategize
#### Explain
When to use it
You're staring at a concept, a function, or a behaviour you don't fully understand. You want to get it — not just work around it.
You'll recognise this when you say
- "What does X actually do?"
- "I know it works, but I don't know why."
- "Can you explain filter context to me?"
- "What's the difference between CALCULATE and CALCULATETABLE?"
Prompt Workshop — click any underlined part Copy Explain what CALCULATE does in DAX, including how it modifies filter context . I'm comfortable with Excel SUMIF logic but new to DAX . Walk me through a concrete example using a Sales table with Date and Amount columns . End with a one-sentence rule of thumb I can remember. Goal: The specific concept you want explained. "Explain CALCULATE" beats "explain DAX" — narrow it down. Your context: Your knowledge level calibrates the vocabulary and analogies Claude uses. Always include it. Concrete example: Anchors the explanation in reality. Abstract explanations of DAX rarely stick. Output format: A rule of thumb, a one-liner, a mental model — asking for it improves retention. Goal Your context Concrete example Output format Try these variants
Explain what CALCULATE does in DAX, including how it modifies filter context . I'm comfortable with Excel SUMIF logic but new to DAX . Walk me through a concrete example using a Sales table with Date and Amount columns . End with a one-sentence rule of thumb I can remember. '>CALCULATE Row vs Filter Context Relationships Star Schema
#### Build
When to use it
You need something written from scratch — a DAX measure, an M transformation, a calculated column, or a report layout. You know what it should do; you need the code.
You'll recognise this when you say
- "Write me a measure that..."
- "I need a Power Query step that..."
- "Give me the DAX for a 13-week rolling average."
- "How do I parameterise this M query?"
Prompt Workshop — click any underlined part Copy Write a DAX measure that calculates year-over-year revenue growth as a percentage . My fact table is 'Sales' with columns 'Revenue' (decimal) and 'OrderDate' (date). I have a Calendar table marked as the date table . Return BLANK when there is no prior year data — not zero . Add a short comment above each logical block explaining what it does. Goal: State exactly what the measure must calculate. "YoY revenue growth %" is specific. "A useful measure" is not. Table & column names: Claude will write syntactically valid DAX using invented names if you don't provide real ones. Always give exact names and data types. Edge cases: BLANK vs zero is one of the most common Power BI mistakes. Specify your expected behaviour upfront so Claude doesn't guess. Output format: Asking for inline comments turns the output into something you learn from — not just paste in and forget. Goal Table & column names Edge cases Output format Try these variants
Write a DAX measure that calculates year-over-year revenue growth as a percentage . My fact table is 'Sales' with columns 'Revenue' (decimal) and 'OrderDate' (date). I have a Calendar table marked as the date table . Return BLANK when there is no prior year data — not zero . Add a short comment above each logical block explaining what it does. '>YoY Growth Rolling 13-Week M Function Scorecard Set
#### Debug
When to use it
You have code that is broken, or a visual that behaves unexpectedly. The quality of Claude's diagnosis depends entirely on how well you describe the problem — this is the most important conversation type to get right.
You'll recognise this when you say
- "This measure returns the wrong number."
- "Power Query throws an error I don't understand."
- "The visual shows X but I expect Y."
- "It works on some rows but not others."
Prompt Workshop — click any underlined part Copy This DAX measure returns total revenue for all time, ignoring my date slicer . Code: Revenue = CALCULATE(SUM(Sales[Revenue]), Sales[Channel]="Online") . I have a Calendar table marked as the date table, with a slicer on Calendar[Year]. The channel filter works but the year slicer is ignored . I expect it to show Online revenue for the selected year only . Explain why this is happening before you give me the fix. Symptom: Describe what you observe — not your theory. "Ignoring the slicer" is a symptom. "Wrong filter context" is already an interpretation; let Claude make that call. Code + model context: Paste the actual code every time. Also describe your relationships and table setup — DAX bugs are almost always model bugs in disguise. Expected vs actual: Claude needs both sides to diagnose correctly. "Wrong results" is not enough. Explain before fix: Asking for the explanation first means you learn something — and it helps you catch a wrong diagnosis before you act on it. Symptom Code + model Expected vs actual Explain before fix Try these variants
This DAX measure returns total revenue for all time, ignoring my date slicer . Code: Revenue = CALCULATE(SUM(Sales[Revenue]), Sales[Channel]="Online") . I have a Calendar table marked as the date table, with a slicer on Calendar[Year]. The channel filter works but the year slicer is ignored . I expect it to show Online revenue for the selected year only . Explain why this is happening before you give me the fix. '>Slicer ignored Power Query error Wrong grand total Circular dependency
#### Critique
When to use it
Something is working — but you're not sure it's working well. You want a second opinion on the logic, performance, readability, or design. Nothing is broken; you just want better.
You'll recognise this when you say
- "This works — is there a better way?"
- "My measures are getting long and hard to read."
- "Does this report make sense for the audience?"
- "Is there a performance risk with this approach?"
Prompt Workshop — click any underlined part Copy Critique this DAX measure for readability and performance . Code: Net Margin % = DIVIDE(SUM(Sales[Revenue])-SUM(Sales[COGS]),SUM(Sales[Revenue]),0) . Used in a matrix with ~500K rows today, scaling to 5M . Be specific — show me the rewritten version, not just advice . Rate the current version 1–10 for each dimension before and after your changes. Critique dimension: Name what you want critiqued — readability, performance, business logic, or design. "General feedback" produces vague output. Scale & usage: A measure in a 10-row summary has different requirements than one in a 5M-row matrix. Always give Claude the scale context. Show, don't tell: "Show me the rewritten version" is more useful than "tell me what to change." Concrete output is always better. Before/after rating: Asking for a score forces specificity — and gives you a benchmark you can reason about. Critique dimension Scale & usage Show rewritten version Before/after rating Try these variants
Critique this DAX measure for readability and performance . Code: Net Margin % = DIVIDE(SUM(Sales[Revenue])-SUM(Sales[COGS]),SUM(Sales[Revenue]),0) . Used in a matrix with ~500K rows today, scaling to 5M . Be specific — show me the rewritten version, not just advice . Rate the current version 1–10 for each dimension before and after your changes. '>Measure quality Report layout Model structure Calc cols vs measures
#### Strategize
When to use it
You have a goal but no clear path. A stakeholder request, a vague brief, or a dataset you don't know what to do with. The Strategize conversation helps you decide what to build before you build it — and saves you from rebuilding it three times.
You'll recognise this when you say
- "I have a dataset — where do I even start?"
- "My stakeholder wants 'a dashboard'. What does that mean?"
- "What measures should I build for this use case?"
- "Is this the right approach before I go further?"
Prompt Workshop — click any underlined part Copy Help me plan a Power BI report for regional sales managers to identify underperforming reps before monthly review . My data includes: Sales (rep name, region, product, date, revenue, units), Targets (rep name, month, revenue target), and HR (rep name, hire date, manager) . Managers are non-technical — they'll look at this for 5 minutes before a meeting . Give me: (1) the 4–5 key measures to build, (2) the recommended visuals and layout, (3) any model work I should tackle first. Business outcome: "Identify underperforming reps" is the business goal. "Build a sales dashboard" is a delivery format. Claude reasons much better from the former. Tables & columns: Claude cannot advise on what to build without knowing what data you have. A one-line table inventory is enough to unlock real recommendations. Audience & usage: Non-technical users, time pressure, meeting context — these change every recommendation. Include them every time. Structured plan: Ask for a checklist: measures, visuals, model work. Claude will default to narrative if you don't specify structure. Business outcome Tables & columns Audience & usage Structured plan Try these variants
Help me plan a Power BI report for regional sales managers to identify underperforming reps before monthly review . My data includes: Sales (rep name, region, product, date, revenue, units), Targets (rep name, month, revenue target), and HR (rep name, hire date, manager) . Managers are non-technical — they'll look at this for 5 minutes before a meeting . Give me: (1) the 4–5 key measures to build, (2) the recommended visuals and layout, (3) any model work I should tackle first. '>Sales report New dataset Performance triage Excel migration Ready to use
### Prompt Patterns Library
Copy and adapt. Replace the italicised parts with your specifics.
Explain Copy Explain [concept] in DAX/Power Query. I have experience with [your background]. Use a concrete example with a [table name] table. End with one rule of thumb I can remember.
Build — DAX Copy Write a DAX measure that [what it calculates]. My fact table is '[TableName]' with columns '[Col1]' and '[Col2]'. Return BLANK (not zero) when [edge case]. Add comments explaining the logic.
Build — M Copy Write a Power Query M transformation that [what it does]. My source table has these columns: [describe]. The output should [describe result]. Show me the M code and explain each step.
Debug Copy This DAX/M code isn't working: [paste code]. I expected [expected result] but I'm getting [actual result]. My model: [brief description]. Explain what's causing this before you give me the fix.
Critique Copy Critique this [measure/model/report] for [readability / performance / logic / design]: [paste or describe]. Show me the improved version — not just advice. Rate it 1–10 before and after.
Strategize Copy I need a Power BI report for [audience] to help them [business goal]. My data: [list tables and key columns]. Audience is [technical level], using this [usage context]. Give me: key measures to build, recommended visuals, and model work to tackle first.
Getting more from Claude
### Pro Tips
Common mistakes — and how to sidestep them.
Always paste the actual code — never describe it + "I have a CALCUL

[truncated — full text at https://endash.us/toolkit/items/claude-powerbi-scroll]

---

# Context Graphs

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/what-are-context-graphs
- **Tags**: ai, alignment

Skip to main content Context Graphs
- Progression
- Anatomy
- In practice
- Builder
- Craft
- Start
A working primer
## Context graphs are how you ship reasoning , not just retrieval .
Most of what an organization knows doesn’t live in any one document; it lives in the connections between things:
- Who works with whom
- What depends on what
- Which decision led to which outcome
A context graph is how you write those connections down in a form a machine can actually use.
Start the primer Skip to the builder Written for Engineers & PD Reading time ~15 min Take away Exportable YAML / JSON / Cypher 01 The progression
### Eight steps from language models alone to a graph that learns from itself.
The idea isn’t new. Knowledge-representation people have been working the shape for sixty years. What’s new is that language models can finally read it. Here’s the road — click through to see where the industry actually sits today.
step_01 LLM alone step_02 RAG step_03 GraphRAG step_04 Ontology RAG step_05 Tuned retrieval step_06 Self-describing step_07 Dynamic step_08 Closing the loop 2020 and earlier LLMs answer from their training data. Fast, fluent, locked to what the model saw during training. No knowledge of your business, your customers, your deploy from Tuesday. Every wrong answer is stateless — the model can’t even tell you why.
Context Engineering has always felt like a better fit to me, but it just hasn’t seemed to gain traction, until perhaps now?
Daniel Davis &middot; Context Graph Manifesto &middot; Dec 2025 02 Anatomy
### The unit: subject, predicate, object.
At the bottom of every context graph is the same three-part fact. Two things and the relationship between them. That’s it. Everything above this — ontologies, Cypher, Turtle, RDF, the entire stack — is what you do with many of these, connected.
Try it in context: Team Services Codebase Incident Learning Maya memberOf Platform A person and the team they’re part of.
Subject Maya The thing the fact is about. Usually an entity — a person, a service, a commit, a concept. Predicate memberOf The relationship. Verb-like, specific. This is the piece engineers almost always underspecify — “is_related_to” is a tell. Object Platform Another entity, or a literal (a timestamp, number, identifier). Typed when it matters. 03 In practice
### Where they’re already doing real work.
You’ve probably seen one of these this year without calling it a context graph. These are the shapes that show up most often when a team needs structure, not just search.
case_01 Agent memory case_02 Audit & provenance case_03 Multi-hop queries case_04 Temporal reasoning case_05 Ops & dependencies 04 Hands on
### Build a context graph. Export it as YAML, JSON, Cypher, or Turtle.
Pick a domain. Add nodes. Connect them with predicates. The objective banner shows you what the graph is trying to capture at each step. When it’s shaped right, copy it out — that’s a working seed for a real context graph in TrustGraph, Neo4j, or any RDF store.
Graph builder Team & roles Service deps Incident trace Learning path Blank Represents People and the teams they’re part of. From side People, current roles. To side Teams, scopes, managers. From 0 nodes Add Before connecting: what does this relationship actually mean? That’s your predicate. Bad predicates are the #1 cause of bad graphs. Drag nodes to reposition Connect two nodes Connect To 0 nodes 0 triples Add Export YAML JSON Cypher Turtle Copy Reset That export isn’t a toy. It’s the same shape you’d seed a TrustGraph context core with, or load into Neo4j with a LOAD CSV . The structure is the product.
You’ve already done the hard part 05 New craft
### Three shifts that change how you ship software.
Context graphs don’t just unlock features. They shift what “good engineering” looks like. A few changes worth naming before the language settles.
shift_01
#### Structure is the product.
The ontology is no longer backend detail. It’s a design deliverable.
What entities does the system recognize? What predicates connect them? These decisions shape what users can ask, what the agent can answer, and what can be audited afterwards. A sloppy ontology produces a sloppy system no matter how good the model is.
shift_02
#### Reasoning leaves a trail.
Decisions become graph data. Every “why” is queryable.
When the agent’s chain of thought, the triples it looked at, and the model parameters in effect all live in the graph, you stop debugging with print statements and start asking the graph itself: why did we recommend this? This is the piece regulated shops have been waiting for.
shift_03
#### Context becomes portable.
“What the system knows” ships between teams like code.
Context cores — versioned bundles of knowledge, embeddings, policies — start to look like libraries. You build one, test it, tag it, promote it across environments. Institutional knowledge stops living in heads and starts living in packages.
06 Get started
### A short path in, if this is new.
Two open-source projects worth your afternoon, and a five-item checklist to walk the first mile. Nothing below requires a platform contract.
Scaffold
##### create-context-graph
Neo4j Labs’ CLI. Pick a domain, pick an agent framework (PydanticAI, Claude Agent SDK, LangGraph…), get a running app with streaming chat, graph viz, and decision tracing. Four commands.
create-context-graph.dev &rarr; Platform
##### TrustGraph
Apache-licensed. Graph-native storage (Cassandra default, Neo4j supported), semantic retrieval pipelines, portable context cores you can version and promote like code.
trustgraph.ai &rarr; Reading
##### Context Graph Manifesto
Daniel Davis, 16 minutes. The clearest piece of writing in the space. Walks the full evolution, from someone who has been at the problem for eighteen months.
Read the manifesto &rarr;
#### The first mile
Name one dataset at work that is really a graph You already have one. Services and their deps. Tickets and the decisions that closed them. Commits and the authors + reviewers. The question isn’t whether the graph exists — it’s whether anything is using it as one. Write five triples about it by hand Subject, predicate, object. The point isn’t the triples — it’s finding out which predicates you don’t have good names for. That’s where the ontology work actually lives. Read the Context Graph Manifesto Sixteen minutes, no hype. You’ll finish with a clearer picture of where RAG stops and where context engineering starts. Scaffold a throwaway app with create-context-graph Pick a domain you know. Let demo data seed the graph. Poke at the decision traces. Four commands, nothing to uninstall cleanly. Decide whether you want structure or similarity Usually both. If you need both, a context graph stops looking like an option and starts looking like the default.
### Context is the unit of work now.
If you’re thinking about where this fits for your team — what it replaces, what it doesn’t, what to try first — we’d be glad to talk it through. En Dash works at the seam between new technology and how organizations actually ship.
Start a conversation Try create-context-graph En Dash Consulting &middot; Context Engineering &middot; 2026

---

# Copilot and Microsoft 365, Workflows & Governance

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/copilot-ms365-workflows-scroll
- **Tags**: ai, communication, collaboration, agile, prompts, governance, compliance, guide

Skip to main content
- Overview
- Workflows
- Prompt Builder
- Governance
- Custom Tools
- Overview
- Workflows
- Prompt Builder
- Governance
- Custom Tools
Dark mode Microsoft 365 Copilot Excel &middot; Word &middot; PowerPoint
## You have Copilot. Now build a system around it.
Most teams use M365 Copilot for one-off tasks and forget about it between them. This guide shows you how to build repeatable workflows in Excel, Word, and PowerPoint — plus the governance guardrails to deploy it safely.
Explore workflows → Governance checklist Copilot is live in XL Excel Formulas, data analysis, Agent Mode for multi-step workbook tasks Formulas Analysis Agent Mode Active W Word Drafting, rewriting, sensitivity label inheritance, Agent Mode (GA) Draft Rewrite Agent Mode Active PPT PowerPoint Create from file, bulk reformatting, speaker notes, Designer integration Create Speaker Notes Designer Active The Problem
### Copilot as a habit vs. Copilot as a system
When Copilot is something you remember to try, you get inconsistent results and no compounding value. When it's embedded in a defined workflow, it multiplies your output every time.
Habit mode
#### What most teams do
- Write a prompt from scratch each time
- Use Copilot for whichever task comes to mind first
- No shared prompts across the team
- No governance — Copilot can see everything
- Results vary wildly, trust erodes
System mode
#### What you could do instead
- Saved, reusable prompts for each recurring task
- Defined entry points per app and workflow type
- Team prompt library stored in SharePoint
- Sensitivity labels and DLP policies in place first
- Predictable outputs the whole team relies on
Repeatable Workflows
### Pick your app. Build the loop.
Each app has a different interaction model. Understanding where Copilot fits inside each one is the first step to replacing one-time asks with repeatable systems.
Excel Word PowerPoint Formula & Analysis
#### Explain & write complex formulas
Tell Copilot what you want to calculate. It writes the formula, explains each part, and flags edge cases — without you leaving the grid.
Data Shaping
#### Clean and reshape messy data
Paste in raw exports. Ask Copilot to remove blanks, normalise columns, split fields, or convert formats — described in plain English.
Insight Generation
#### Surface trends and anomalies
Highlight a range and ask Copilot to identify what's notable. Get a plain-language summary plus a suggested chart type to illustrate it.
Agent Mode
#### Multi-step workbook tasks
Agent Mode in Excel can plan and execute multi-step tasks — building models, reshaping tables, generating charts — while you watch and verify each step.
Excel — Formula & Analysis
#### Explain & write complex formulas
Close × 1 Open Copilot in ExcelClick the Copilot button in the Home ribbon. Make sure you have data in a named table — Copilot performs best when it can reference structured ranges.
2 Describe what you needDon't write the formula — describe the output. Use this prompt template:
Write a formula that calculates [WHAT] for each row in column [COLUMN], using the values in [SOURCE COLUMNS]. Flag any rows where [EDGE CASE CONDITION]. Explain each part of the formula. 3 Review, then insertCopilot shows the formula and its explanation before inserting. Read it. If the logic is wrong, tell it what to fix before committing. Click "Insert column" only when you're satisfied.
4 Save this prompt to your libraryCopy the working prompt into your team's shared prompt library in SharePoint. Tag it with the workflow name and the table structure it works for.
Excel Copilot in Grid Formula Writing Excel — Data Shaping
#### Clean and reshape messy data
Close × 1 Load the raw dataPaste your export into a new sheet. Convert it to a Table (Ctrl+T) so Copilot has a clear reference for column names and structure.
2 Describe the transformation In the [TABLE NAME] table: remove rows where [COLUMN] is blank, split the [COLUMN] column into separate First Name and Last Name columns, and convert all dates in [DATE COLUMN] to YYYY-MM-DD format. Add a new column called "Status" with the value "Active" for all rows. 3 Verify before savingUse Ctrl+Z to undo any changes that aren't right. Copilot works incrementally — you can correct one step without losing the others.
Excel Data Cleaning Table Operations Excel — Insight Generation
#### Surface trends and anomalies
Close × 1 Select your data rangeHighlight the table or range you want analysed. The more structured the data, the more useful Copilot's analysis will be.
2 Ask for a narrative summary Analyse this data and tell me: what are the top 3 trends, are there any outliers or anomalies I should flag, and what chart type would best illustrate the key pattern? Keep it to 3 sentences max. 3 Generate the chartAsk Copilot to insert a recommended chart. Then use the chart title and axis labels it suggests as the basis for your deck's slide copy.
Excel Analysis Charting Excel — Agent Mode
#### Multi-step workbook tasks
Close × 1 Enable Agent ModeAgent Mode is available in Excel on Windows and Web for Microsoft 365 Copilot subscribers. Open Copilot and look for the Agent Mode toggle at the top of the panel.
2 Describe the full task Build a monthly budget model from the data in Sheet1. Create summary tables by category, add variance columns comparing to the prior month, generate a waterfall chart showing the top 5 cost drivers, and format the final sheet for printing. 3 Stay in controlAgent Mode shows you each step before executing it. Approve, modify, or stop at any point. Your data is never changed without your confirmation.
Excel Agent Mode Complex Models Document Creation
#### Draft from a brief or source file
Give Copilot a brief, a reference doc, or both. It generates a full structured first draft — sections, headings, and opening paragraphs — in your format.
Editing & Tone
#### Rewrite for audience or length
Select a passage and tell Copilot who's reading it. It adjusts register, cuts jargon, or expands thin sections — without losing the core argument.
Templates
#### Build reusable document templates
Define a standard structure for recurring document types — briefs, SOPs, status reports — and embed Copilot instructions directly in the template notes.
Agent Mode
#### Iterative long-document editing
Agent Mode in Word is generally available. It can make direct edits across a full document, apply formatting consistently, and restructure sections based on your instructions.
Word — Document Creation
#### Draft from a brief or source file
Close × 1 Start with Draft with CopilotIn a new document, click "Draft with Copilot" in the canvas. This gives Copilot access to the full document context from the start.
2 Reference a source fileUse the "/" reference syntax to point Copilot at an existing file. It pulls structure and content from the source while writing in the new document.
Draft a [DOCUMENT TYPE] based on /[SOURCE FILE]. Use the following sections: [SECTION 1], [SECTION 2], [SECTION 3]. Audience: [AUDIENCE]. Tone: [TONE]. Length: approximately [TARGET LENGTH]. 3 Sensitivity label inheritanceWhen Copilot drafts from a labelled source file, the new document inherits the source's sensitivity label. Verify the label shown at the top of the document before sharing.
Word Draft with Copilot Label Inheritance Word — Editing
#### Rewrite for audience or length
Close × 1 Select the passageHighlight the paragraph or section. Click the Copilot icon that appears in the margin, or open the Copilot panel and reference the selection.
2 Give a specific rewrite instruction Rewrite this section for [AUDIENCE TYPE, e.g. "a non-technical executive audience"]. Keep the core argument. Cut jargon. Target [WORD COUNT]. End with a clear call to action. 3 Accept, discard, or iterateCopilot shows the rewritten version alongside the original. Use "Regenerate" to get a different take before accepting. Track changes stays on so reviewers can see what changed.
Word Rewrite Tone Adjustment Word — Templates
#### Build reusable document templates
Close × 1 Define your document structureCreate a Word template (.dotx) with your standard sections. In each section's notes or placeholder text, embed the Copilot prompt that should generate that section's content.
2 Embed prompts as instructional text [COPILOT: Draft a 2-paragraph executive summary of the project described above. Audience: C-suite. Tone: direct and confident. Do not use bullet points.] 3 Store in SharePoint, not locallySave templates to a shared SharePoint library with the correct sensitivity label. This ensures every team member uses the same version and Copilot can reference them via the "/" syntax.
Word Templates SharePoint Word — Agent Mode
#### Iterative long-document editing
Close × 1 Agent Mode is generally availableFor Microsoft 365 Copilot subscribers, Agent Mode in Word requires no special activation. Open the Copilot panel and it will offer agentic capabilities automatically for complex tasks.
2 Describe the full editing task Review this entire document. Standardise all heading levels, replace informal language with formal equivalents, ensure the conclusion references points made in sections 2 and 4, and add a summary table after the introduction listing all recommendations. 3 Review each changeAgent Mode shows you a step-by-step plan before making changes. Approve the plan, then review each edit in track-changes mode before accepting.
Word Agent Mode Long Docs Deck Creation
#### Create a presentation from a document
Point Copilot at a Word document or brief. It builds a structured deck with one idea per slide, a suggested visual layout, and speaker note starters.
Slide Editing
#### Redesign and reformat slides in bulk
Tell Copilot to standardise your slide layouts, apply a consistent tone to all bullets, or restructure a section — across the whole deck at once.
Explain This
#### Decode complex slides on the fly
Select any text box, table, or acronym and ask Copilot to explain it. Useful for inherited decks or onboarding new team members to existing materials.
Speaker Notes
#### Generate and improve speaker notes
Ask Copilot to write speaker notes for every slide, calibrated to the audience and the time you have per slide. Edit the result before you present.
PowerPoint — Deck Creation
#### Create a presentation from a document
Close × 1 Start in a new presentationOpen PowerPoint and click "Create presentation from file" in the Copilot panel. Reference a Word document, PDF, or outline stored in SharePoint or OneDrive.
2 Define the deck's parameters Create a [NUMBER]-slide presentation based on /[SOURCE FILE]. Audience: [AUDIENCE]. Purpose: [PURPOSE, e.g. "board update", "client pitch", "team training"]. One key idea per slide. Include speaker notes of [LENGTH] per slide. 3 Check the inherited labelWhen creating from a labelled source, the presentation inherits that label. Check it before sharing — if the label is more restrictive than needed, you can adjust it, but not to a lower sensitivity than the source.
PowerPoint Create from File Label Inheritance PowerPoint — Slide Editing
#### Redesign and reformat slides in bulk
Close × 1 Open the Copilot panelWith your deck open, use the Copilot panel to issue instructions that apply to the whole deck. You don't need to select individual slides for bulk operations.
2 Issue a bulk editing instruction Across all slides: standardise all bullet points to no more than 8 words each, remove any slide with fewer than 2 content items, and ensure every slide has a clear action-oriented headline. Apply consistent capitalisation to all titles. 3 Use Designer for visual consistencyAfter Copilot edits content, use PowerPoint Designer to suggest layout improvements. These two tools work in sequence — content first, then visual treatment.
PowerPoint Bulk Editing Designer PowerPoint — Explain This
#### Decode complex slides on the fly
Close × 1 Select any elementThe "Explain this" feature works on text boxes, tables, acronyms, or entire slides. Select the element, then open the Copilot panel. It provides contextual explanation without modifying the slide.
2 Ask follow-up questions Explain the acronym [ACRONYM] in the context of this slide. Then suggest a clearer alternative phrasing for the ma

[truncated — full text at https://endash.us/toolkit/items/copilot-ms365-workflows-scroll]

---

# CSS Scroll-Margin-Top vs Scroll-Padding-Top

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/scroll-margin-top-vs-scroll-padding-top
- **Tags**: ui, development, guide, design, ux

Skip to main content
- Live Demo
- Context
- The Properties
- Which One?
- Gotchas
Dark CSS Scroll Behavior — En Dash Reference
## Your nav bar is eating your headings.
Two CSS properties fix it. They're not the same. Here's the demo first, then the explanation.
scroll-padding-top scroll-margin-top At a Glance
### scroll-margin-top vs scroll-padding-top: the difference
scroll-padding-top | scroll-margin-top
Goes on | The scroll container ( html or any element that scrolls) | The scroll target — the element you jump to
Scope | One declaration covers every anchor jump in the container | Per element — each target sets its own offset
Negative values | ✕ Not allowed | ✓ Valid
Percentages | ✓ Accepted | ✕ Silently ignored (lengths only)
Also affects | scroll-snap alignment of children | scrollIntoView() landings and the snap area
Reach for it when | One sticky header, same offset everywhere | Different offsets per element, or nested scroll containers
01 Live Demo
### See it land
A scroll container with its own sticky header. Pick a mode, jump to any section, watch where the heading lands. The teal line marks the offset boundary when a fix is active. Switch modes and re-click the same button to compare directly.
Mode: No fix scroll-padding-top scroll-margin-top Scroll container
Sticky Nav Content above first section… Section One Does the heading clear the bar, or slide beneath it? That's the whole question.
Section Two Taller content to give enough scroll range to show the offset clearly.
More content — more content — keep going.
Section Three Switch modes, re-click the same link. Compare the exact landing position.
Section Four Same result, different architecture. That's the whole lesson.
Jump to section
→ Section One → Section Two → Section Three → Section Four Mode: No fix Applied CSS: none 02 Context
### Same fix. Different owner.
You have a sticky nav. You have anchor links. The browser scrolls the target to the top edge of the scrollport — directly behind your bar. The old workaround was a ghost element: margin-top: -80px; padding-top: 80px on every target. Works until nav height changes. Works until someone deletes it.
"The browser isn't wrong. It put the element at the top. You just forgot something already lives there." Both properties offset where "arrived" means. The only distinction is which element each goes on.
Where each property lives in the DOM scroll-padding-top — on the container
┌ <html> scroll-padding-top: 64px ├ <nav> sticky, 64px ├ <section id="a"> └ <section id="b"> One declaration. Every anchor jump in the container respects it.
scroll-margin-top — on the element
┌ <html> ├ <nav> sticky, 64px ├ <section id="a"> scroll-margin-top: 64px └ <section id="b"> scroll-margin-top: 80px Per-element. Each target declares its own offset independently.
The short version: same offset everywhere? Put scroll-padding-top on html once. Different offsets per element, or nested scroll containers? Use scroll-margin-top on the targets.
03 Deep Dive
### The properties
scroll-padding-top scroll-margin-top On the container Insets the scroll container's optimal viewing region from the top. When the browser scrolls to any anchor inside the container, it lands the element within this inset area — not flush with the raw top edge.
Applies to: Scroll containers ✓ Percentages accepted ✕ No negative values Also affects: scroll-snap alignment Shorthand: scroll-padding /* One line. Fixes every anchor link on the page. */ html { scroll-padding-top : 64px ; } /* Tie it to a custom property for easy maintenance */ :root { --nav-h : 64px ; } html { scroll-padding-top : var(--nav-h) ; } /* Works on any scroll container, not just html */ .sidebar { overflow-y : scroll ; scroll-padding-top : 48px ; } Copy
#### Also moves snap points
scroll-padding-top shifts where scroll-snap-align: start children snap, not just where anchor links land. One property on the container. Zero per-item work.
Don't use :root. They select the same element, but the property targets the scroll container. Use the html type selector. :root silently fails.
On the element Expands the target element's scroll snap area outward. The browser acts as if the element starts N pixels higher. Zero layout impact — box model, padding, margin are untouched. Only the scroll algorithm sees this.
Applies to: All elements ✓ Negative values valid ✕ No percentages (silent fail) Layout impact: none Shorthand: scroll-margin /* Per-element, per-target */ #about { scroll-margin-top : 80px ; } #features { scroll-margin-top : 64px ; } /* scrollIntoView() respects it too — no JS offset math */ el.scrollIntoView({ behavior : 'smooth' , block : 'start' }); /* Negative values: scroll-padding-top can't do this */ .overlap { scroll-margin-top : -8px ; } Copy
#### No margin collapsing
Adjacent CSS margins collapse. scroll-margin values do not. Two adjacent sections each with scroll-margin-top: 40px each get the full 40px. Despite the name, these are scroll hints — not box-model margins.
Percentages fail silently. scroll-margin-top: 10% is a parse error. The browser ignores it. Length values only: px , rem , em .
04 Decision Guide
### Which one?
Three questions. First match wins.
Do all your anchor targets need the same offset?
Yes — same everywhere No — different per target → scroll-padding-top on html
One declaration. Done. Tie it to a CSS custom property if nav height might change.
html { scroll-padding-top : var(--nav-height) ; } Copy → scroll-margin-top per element
Set it on each target independently. The container stays untouched.
.sec-a { scroll-margin-top : 80px ; } .sec-b { scroll-margin-top : 40px ; } Copy Do you need a negative offset?
Yes — pull past the edge No — positive only → Must use scroll-margin-top
scroll-padding-top treats negatives as 0 . scroll-margin-top accepts them.
→ Either works
Both properties behave correctly with positive values. Default to whichever fits question one.
Is the target inside a nested scroll container?
Yes — inside overflow: scroll No — regular page scroll → Apply to the inner container, or scroll-margin-top on the target
The browser scrolls the nearest scrollable ancestor. scroll-padding-top on html won't reach it.
→ scroll-padding-top on html
Standard case. One property, done.
05 Edge Cases & Gotchas
### Things the docs gloss over
Click any row to expand.
Naming The names are actively misleading ▾ scroll-margin-top adds no visible margin. scroll-padding-top adds no padding. Both are purely scroll-behavior directives. Neither shows up in the box model or DevTools layout panels.
:root vs html scroll-padding-top on :root does nothing ▾ :root and html select the same element, but the property must target the scroll container context. Use the html type selector. :root silently fails.
Percentages scroll-margin-top rejects percentages without warning ▾ scroll-padding-top: 10% is valid. scroll-margin-top: 10% is a parse error the browser ignores silently. Length values only on scroll-margin: px , rem , em .
Dynamic navs Update when nav height changes ▾ If your sticky nav collapses on scroll, a hardcoded offset is wrong half the time. Store nav height in a CSS custom property, update it via JS, and reference the variable in your scroll offset property.
Nested containers Scroll context is everything ▾ If the target is inside a nested overflow: scroll container, the browser scrolls that container, not the page. scroll-padding-top on html has no effect. Apply it to the inner container, or put scroll-margin-top on the target.
JavaScript scrollIntoView() respects both ▾ element.scrollIntoView({ block: 'start' }) respects scroll-margin-top on the target. Modern browsers also respect scroll-padding-top on the container. No JS offset math needed.
No collapse scroll-margin values don't collapse ▾ Adjacent CSS margins collapse. Adjacent scroll-margin-top values do not. Each element gets its full declared offset when scrolled to.
Reduced motion These are destination properties, not animation ▾ prefers-reduced-motion has no effect on either property. Do still set scroll-behavior: auto inside a reduced-motion query to disable the smooth animation separately.
Browser Support
Browser | scroll-padding-top | scroll-margin-top
Chrome / Edge | ✓ since 69 / 79 | ✓ since 69 / 79
Firefox | ✓ since 68 | ✓ since 68
Safari | ✓ since 14.1 | ✓ since 14.1
IE 11 | ✕ | ✕
Baseline since 2020. Ship it.
En Dash
### Building something that needs to scroll right?
En Dash works with product teams on interactive experiences, design systems, and the front-end problems that live between "it works" and "it's actually good."
Talk to En Dash Read: Modal vs. Modeless →

---

# Developer Experience in an Age of AI

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/dx-and-ai-scroll
- **Tags**: development, devOps, agile, ai, kaizen, continuousimprovement, leadership, alignment, guide

AI
## Developer Experience in the Age of AI
AI hasn't just changed what developers build — it's changed what it means to build at all. The teams winning aren't just moving faster. They're architecting the conditions for intelligence to flow.
Scroll to explore Context is the new code · Friction is the enemy of flow · DX is a team sport · Document the why, not the what · Your README is now a runtime artifact · AI amplifies everything — including the bad · The feedback loop is sacred · Prompts are interfaces — design them · Context is the new code · Friction is the enemy of flow · DX is a team sport · Document the why, not the what · Your README is now a runtime artifact · AI amplifies everything — including the bad · The feedback loop is sacred · Prompts are interfaces — design them · The Central Truth
### AI doesn't fix bad DX. It scales it.
For two decades, developer experience was the thing you improved after shipping the real work. Good tooling made good developers more pleasant. Bad tooling made them slower. That calculus is shattered.
When AI agents write code and navigate your codebase from your documentation, every ambiguity, every missing context, every tangled interface becomes an exponential liability. The age of tolerating friction is over.
The Four Pillars of AI-Era DX 01
#### Context is the New Code
Documentation · READMEs · ADRs · System Prompts
+ Your system prompts, READMEs, ADRs, and inline comments aren't documentation anymore. They're execution artifacts. When an AI agent clones your repo, it inherits every structural decision you've made — clear or cryptic. Treat your context with the same rigor as your code. Version it. Own it. Iterate on it.
- Write READMEs as if an intelligent agent will onboard from them overnight
- Capture architectural decisions in structured ADRs — the "why" matters more than the "what"
- Annotate interfaces with intent, not just signature
- Maintain a living AGENTS.md that tells AI tools how to navigate your repo
- Treat your system prompt as a product: it ships, iterates, and has owners
02
#### The Feedback Loop is Sacred
Velocity · Local Dev · CI/CD · Onboarding
+ How fast can a developer — or an AI agent — go from confused to productive? That latency is your DX score. Every second of uncertainty compounds across every contributor and every sprint. Minimize it obsessively. The feedback loop isn't a nice-to-have. It's the metabolic rate of your team's intelligence.
- Invest in local dev environments that mirror production exactly
- Run tests in under 60 seconds — or developers stop running them
- Make errors legible: stack traces that explain, not just accuse
- Build AI-aware CI/CD that surfaces context at the point of failure
- Design onboarding so a new dev ships something real on day one
03
#### Clarity Compounds
Naming · Interfaces · Conventions · Glossaries
+ Every ambiguity you remove multiplies across every AI interaction that follows. Every point of confusion becomes a tax paid repeatedly — by every engineer, every agent, every sprint. The organizations moving fastest aren't generating the most code. They're working in the clearest systems.
- Name things with the precision of a contract, not the speed of a deadline
- Define shared vocabulary in a version-controlled, owned glossary
- Establish interface contracts before implementation begins
- Review PRs for clarity of intent, not just correctness of code
- Audit your codebase quarterly for "clever" code — rewrite it to be obvious
04
#### Culture Over Tools
Champions · Measurement · Incentives · Practice
+ You can buy every AI coding tool on the market and still have terrible DX. Tools don't care about developers. Teams do. DX is a practice, a posture, a commitment — not a product purchase. The moment a team stops actively improving its own experience, entropy takes hold. The default state is degradation.
- Designate a DX champion — one person whose mandate is removing friction
- Run DX retrospectives: "what blocked you that had nothing to do with the problem?"
- Reward engineers who improve the system alongside those who ship features
- Make documentation a first-class artifact with named owners
- Measure DX: deployment frequency, onboarding time, build speed
DX Five Hard Truths 01
#### Your AI tools are only as good as your codebase's legibility
When Copilot or Claude touches your repo, it inherits every structural decision you've made — good and bad. Tangled dependencies, inconsistent patterns, missing context: the AI doesn't fix these. It reproduces them at scale, with confidence, at velocity.
02
#### Speed without clarity is just technical debt moving faster
The promise of AI-assisted development is velocity. But velocity on a poorly designed system produces poorly designed systems faster. The discipline of DX is what makes speed sustainable — and what separates teams that thrive from teams sprinting toward a wall.
03
#### Prompts are interfaces. Design them that way.
The prompts your team writes are interfaces to intelligence. They deserve the same rigor as an API: versioned, documented, tested, owned. Treat ad-hoc prompting the way you treat ad-hoc SQL — as a signal that something needs to be formalized before it becomes an assumption.
04
#### The moat isn't the model — it's what the model works in
Everyone has access to the same foundation models. The differentiator is the environment those models operate in: your codebase, your context, your conventions, your culture. That's the moat no one can replicate. That's what DX builds. That's what compounds over years.
05
#### Developer experience is a leadership responsibility
DX doesn't improve itself. Someone has to own it, advocate for it in planning sessions, and protect time for it. If leadership doesn't care how developers experience their work, it will always lose to feature velocity — right up until it catastrophically doesn't.
3× More code reviewed per day with intentional DX + AI 70% Of AI coding errors trace back to missing or ambiguous context Day 1 When great DX makes first commits possible Context as Infrastructure
### Your README is now a runtime artifact.
When an AI agent clones your repository, it reads before it writes. The quality of your documentation isn't just a human-experience concern — it's a correctness concern. Unclear context produces incorrect code, delivered with perfect confidence.
Structure your context intentionally. Version it. Test it. The AGENTS.md pattern emerging across leading teams is a signal: the organizations moving fastest are treating context as infrastructure, not annotation.
AGENTS.md # AGENTS.md — Context for AI tools # Version this. Own this. Update this. ## Architecture Next.js 14 app / Supabase backend State: Zustand. No Redux. No exceptions. ## Conventions - Components: /src/components/{domain}/ - Server actions: /src/actions/ - Never mutate Zustand state directly - Use logger util, not console.log - All DB calls through the service layer ## Hard boundaries - Do NOT use legacy /api/v1 routes - Do NOT add deps without a comment - Do NOT skip schema validation ## Testing pnpm test -- --watch Coverage: 80% minimum # Tests under 60s. Non-negotiable. ## When lost Read /docs/architecture.md first. Context is cheap. Assumptions are not. The Practical Playbook
### Start here. Ship this week.
Good intentions don't improve DX. Specific, executable actions do. Find your lane.
For Individual Devs For Tech Leads For Organizations
##### Write an AGENTS.md today
Add a file that explains the codebase to AI tools: architecture, conventions, gotchas, where to start. A map for intelligent navigators.
30 min task
##### Audit your personal feedback loop
Time yourself from "I have an idea" to "it's running locally." Every minute over ten is friction to eliminate.
This sprint
##### Version your best prompts
Keep a .prompts/ directory. Check in the ones that work. Review when outputs drift. Own them like code.
Ongoing habit
##### Write one ADR per major decision
Architecture Decision Records capture what you decided and why. Gold for future-you, new teammates, and AI tools navigating your system.
Per feature
##### Refactor one "clever" thing weekly
Pick one piece of code that's hard to explain to a human — or an AI. Rewrite it obvious. Document the trade-off. This compounds.
Weekly habit
##### Read your own README cold
Imagine you're joining tomorrow. Can you follow your README to a running app? Fix where it breaks. Then imagine an AI doing the same.
This week
##### Run a DX Retrospective
Add a standing agenda item: "What blocked you this week that had nothing to do with the problem itself?" Friction surfaces fast when you ask. Then fix it.
Next sprint
##### Measure onboarding time
Track time-to-first-commit for every new engineer. Set a Day 1 target. Review what blocked them. Iterate on the setup experience like a product.
Process change
##### Designate a DX owner
Assign one engineer per quarter whose primary mandate is DX improvement. Not a committee — one accountable person with budget and authority.
Structural
##### Instrument your build pipeline
If your build time is a mystery, it'll never get faster. Measure it. Set a threshold. Put it on a dashboard. Treat build regression as a performance bug.
Infrastructure
##### Establish AI usage conventions
Don't leave AI tool usage to individual improvisation. Codify which models, which contexts, how to handle generated code in PRs.
Team norms
##### Reward the meta-work
Publicly recognize engineers who improve documentation, sharpen tooling, write cleaner interfaces. If only features get celebrated, only features get invested in.
Culture
##### Fund Platform Engineering
Internal developer platforms are one of the highest-leverage investments an org can make. A team of 3 PEs can multiply the productivity of 50 product engineers.
Investment
##### Track DORA metrics
Deployment Frequency, Lead Time, Change Failure Rate, MTTR. These four metrics tell you more about DX health than any survey. Start measuring.
Measurement
##### Build a secure AI enablement layer
Developers will use AI with or without policy. Build guardrails that enable rather than restrict: approved models, vetted MCP servers, audit logging.
Architecture
##### DX as strategic moat
As AI commoditizes feature development, the differentiator shifts to the system where development happens. Your architecture and context aren't overhead — they're IP.
Strategic
##### Teach prompt engineering as a core skill
Writing good prompts is a craft, like writing good SQL. Train your engineers. Run workshops. Build internal prompt libraries. The productivity gap will be measured in prompt quality.
L&D
##### Standardize context delivery
Don't let every developer separately explain your system to AI. Build org-wide context packages: shared system prompts, repo maps, standards — injected consistently.
Infrastructure Who Does What
### DX is everyone's job. Not anyone's burden.
Individual Developers
- Own the quality of context you leave behind — for the next human, and the next agent
- Invest 10% of your time improving your own tools and workflow
- When you hit friction, file an issue — don't just silently work around it
- Write code for the reader, not the compiler
- Treat your prompts as craft — iterate on them, share the good ones
- Say something when the onboarding doc is wrong
Tech Leads & Managers
- Protect time for DX work in every sprint — it's not optional, it's load-bearing
- Create a visible channel for DX feedback and act on it visibly
- Celebrate the engineer who reduced build time alongside the one who shipped a feature
- Define what good AI-augmented workflow looks like for your team, explicitly
- Make the hard architectural calls that reduce complexity for everyone who follows
- Hire for clarity of communication, not just technical depth
Organizations & Leaders
- Recognize that developer experience is a competitive advantage, not overhead
- Fund the platform work that doesn't ship features but enables everything else
- Set DX improvement goals with real accountability at the organizational level
- Measure time-to-productivity and treat regression as a P1
- Build an AI adoption strategy grounded in quality, not just speed
- Create safe channels for developers to surface DX

[truncated — full text at https://endash.us/toolkit/items/dx-and-ai-scroll]

---

# En Dash’s AI Governance Workshop

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/en-dash-ai-governance-workshop
- **Tags**: focus, career, culture, collaboration, scaling, goals, outcomes

Skip to main content
- Why It Exists
- Who It Serves
- What You Get
- Outcomes
- How It Works
Light
- Why It Exists
- Who It Serves
- What You Get
- Outcomes
- How It Works
En Dash — AI Governance Workshop
## Govern AI where it already lives.
A focused working session that turns diffuse AI adoption into a structured governance model — with clear ownership, ranked priorities, and a 90-day execution plan your team can use immediately.
Format Focused working session Outputs 4 working deliverables Horizon 90-day execution path Scroll AI use is advancing faster than the operating models designed to govern it. The workshop exists to close that gap before the cost of waiting becomes visible.
01
### Why it exists
Organizations need visibility into how AI is being used, ownership for how it is governed, and a practical basis for prioritizing what matters most. Right now, most have fragments of each.
01
##### AI is influencing workflows whether or not governance is ready
Usage is active across reporting, analysis, and day-to-day work. Governance built later compounds the gap.
02
##### Ownership exists but is distributed and inconsistent
Teams assume someone else owns review, policy, and accountability — until a decision makes the gap visible.
03
##### Leadership lacks a structured basis for prioritization
Without ranked priorities, governance attention follows whatever concern was raised most recently.
02
### Who it serves
1
#### New or forming governance groups
Organizations building a governance structure for AI for the first time, or refining one that was assembled reactively.
Formation & Structure 2
#### Lean teams with execution responsibility
Teams that need enough rigor to govern well without adding overhead that exceeds their capacity to sustain it.
Lean Operations 3
#### Organizations with AI across multiple tools and platforms
Especially relevant where AI is active across enterprise tools, data platforms, and workflow systems — and no single team has the full picture.
Distributed Environments 03
### What you get
01 AI Use Inventory Foundational Output This creates a grounded view of where AI is already influencing workflows, reporting, and decisions — essential before governance attention can be assigned with confidence.
##### What Becomes Visible
Current usage across core productivity, data, and workflow tools, plus adjacent workflows.
##### Why It Matters
It prevents governance from being built around guesswork or the loudest recent concern.
##### What Leaders Gain
A clearer starting point for deciding where review, ownership, and investment should go first.
##### What It Closes
The gap between broad awareness that AI is present and specific knowledge of where it shapes work.
02 Governance Structure Operating Model Output This translates governance intent into a usable model for ownership, review, risk, and controls in the areas that matter most.
##### What Gets Defined
Ownership, review expectations, and governance responsibilities for priority areas.
##### Why It Matters
Without structure, teams struggle to move from discussion into repeatable decisions.
##### What Leaders Gain
A clearer basis for accountability and cross-functional coordination.
##### What It Closes
The gap between wanting governance and knowing how governance should actually work.
03 Prioritized Use Cases Decision Output This helps the organization identify where governance attention should go first rather than treating every possible AI use as equally urgent.
##### What Gets Ranked
Use cases and areas of activity that deserve governance attention based on organizational reality.
##### Why It Matters
A team that cannot prioritize will spend energy everywhere and gain little traction.
##### What Leaders Gain
A disciplined way to sequence action and justify focus.
##### What It Closes
The gap between concern about AI and practical decisions about where to start.
04 90-Day Roadmap Execution Output This converts the workshop outputs into a practical path the organization can use immediately rather than a static artifact that sits in a folder.
##### What Gets Mapped
Implementation-ready next steps tied to the environment, priorities, and governance structure.
##### Why It Matters
Without a near-term plan, governance efforts lose momentum and credibility quickly.
##### What Leaders Gain
A concrete answer to what happens next after the workshop ends.
##### What It Closes
The gap between alignment in the room and execution after the room clears.
04
### Outcomes
Before the workshop After the workshop
##### Visibility
AI use is happening, but only fragments are visible. Governance attention is shaped by whoever speaks loudest rather than by a complete picture.
AI use inventory establishes where AI is already influencing workflows, reporting, and decisions. Governance effort starts from a grounded view.
##### Ownership
Teams assume someone else owns review or policy interpretation. Roles and decision rights are not clearly defined.
Roles, ownership, and review processes are defined for priority areas. Governance becomes easier to apply consistently.
##### Prioritization
Everything feels important, so little gets sequenced well. The next step remains unclear because there are too many unstructured options.
Defined priority use cases create a clearer starting scope. The 90-day roadmap turns prioritization into sequenced action.
##### Executive Clarity
Conversations stay conceptual or reactive. It is difficult to explain what is happening, what is governed, and what comes next.
Teams can explain where AI is active, how governance is structured, and what the next 90 days will address — without a dense theory deck.
05
### How it works
01
#### Make AI Visible
Create a grounded starting point Map where AI is already influencing workflows, reporting, and decisions.
Surface patterns that are visible, invisible, or inconsistently understood.
02
#### Define Governance
Clarify ownership and review Define ownership, review expectations, and governance responsibilities.
Create a structure that can be used after the session ends.
03
#### Prioritize Action
Focus where governance matters most Identify priority use cases and governance needs based on organizational reality.
Create a sharper basis for executive alignment.
04
#### Build the Plan
Translate outputs into next steps Turn outputs into a practical 90-day roadmap tied to the environment and priorities.
Provide implementation-ready direction for teams and leadership.
Why It Matters Now
#### AI adoption continues whether governance is ready or not.
The practical cost of waiting is fragmented adoption, unclear ownership, and slower executive decision-making about where AI should move next.
What This Supports
#### Better decisions across theory, practice, and execution.
The workshop helps organizations establish enough structure to govern current AI use while creating a clear path for the next 90 days.
AI Governance Workshop
### For organizations that need AI governance to become usable and operational.
A focused working session designed to help teams move from early formation to clear structure, aligned priorities, and a practical 90-day path forward.
Schedule a Conversation Review Deliverables

---

# Getting Started With Atlassian Plans For PMO and VMO Leaders

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/getting-started-with-atlassian-plans-for-pmo-and-vmo-leaders
- **Tags**: jira, tooling, product, project, projectmanagement, pmo, vmo, scrum, planning, atlassian

Skip to main content Start Foundation Scenarios Use cases Need map Planner Rollout Jira Plans for PMOs, project leaders, and agile teams
## When every team has a plan, leaders still need the whole picture.
Jira Plans helps PMOs, project managers, agile leaders, and delivery teams answer the hard questions: which work can fit within available capacity, which dependencies need attention, what changes when priorities shift, and which commitments are at risk.
Test alternate delivery paths See capacity before overload Expose dependency risk early Coordinate work across spaces Scope Bring work together from multiple Jira spaces, boards, filters, and teams so leaders can see delivery as one connected plan.
Scenario Explore alternate timelines, team assignments, releases, and sequencing before committing changes back to Jira.
Capacity Use team capacity, velocity, and sprint information to understand whether the plan is realistic before teams are overloaded.
Risk Make dependencies, warnings, blockers, and off-track work visible earlier, while there is still time to adjust.
Why Jira Plans matters
### A planning layer for work that crosses team boundaries.
The pain usually shows up between team execution and leadership decision-making. Jira work is current, but the cross-team plan is scattered across reviews, spreadsheets, slides, and separate roadmaps. Jira Plans helps turn that into a live planning conversation.
The planning operating layer
#### Three capabilities create the foundation.
Jira Plans is most useful when the question is bigger than one board: Is the release still achievable? Which team is over capacity? Which dependency is putting the program at risk? What should move if leadership changes the priority?
See the whole plan Test the tradeoff Commit the decision 01
#### One planning view across teams
A PMO can look across software, operations, data, security, and business teams without asking each group to maintain a separate status artifact.
Decision enabledSee which initiatives need attention, where work is connected, and where leadership should intervene. 02
#### A safe place to test tradeoffs
Leaders can test a new target date, a reduced scope option, a shifted team assignment, or a changed delivery sequence before changing the underlying Jira work.
Decision enabledCompare options, keep draft changes separate, and commit only the planning decisions that are ready. 03
#### Early warning before plans slip
Plans can surface overloaded teams, dependency timing problems, schedule conflicts, unassigned work, and gaps that would otherwise show up late in the delivery cycle.
Decision enabledAct on capacity, dependency, and schedule risks while there is still time to adjust the plan. Real-world planning moments
### Use Plans when leaders need a clear planning decision.
The strongest use cases are planning conversations where the organization needs to choose whether to keep the date, change the scope, adjust capacity, resequence work, or escalate a dependency.
Planning lever: Scenario modeling
#### Leadership asks to move the target date up by six weeks
A sponsor wants a market launch earlier than planned. The PMO can duplicate the current plan into a scenario, move the target date, and immediately see which epics, teams, and dependencies are affected.
Decision supported
Which scope can stay, which work must move, which team becomes overloaded, and whether the proposed date is realistic.
Planning lever: Capacity tradeoff
#### The same platform team is needed everywhere
Three initiatives all depend on the same architecture or data platform team. Plans helps leaders see the shared constraint, compare timing options, and decide which initiative gets capacity first.
Decision supported
Which work should wait, which dependency needs escalation, and whether adding scope to one project delays other committed work.
Planning lever: Dependency risk
#### A dependency changes the delivery forecast
A team reports on track, but its critical predecessor is late. Dependency views and warning signals help leaders see the downstream effect before the status meeting becomes a surprise.
Decision supported
Whether to resequence work, split the dependent scope, move a milestone, or escalate ownership of the blocker.
Planning lever: Program alignment
#### PI planning needs a cross-team view
Teams can make local commitments while the program still has unresolved cross-team risks. A Program board helps expose dependency chains, handoffs, and timing gaps during the planning conversation.
Decision supported
Which commitments need renegotiation before teams leave planning with conflicting assumptions.
Planning lever: Constraint-based schedule
#### The roadmap no longer matches the current plan
A roadmap has been updated repeatedly through meetings and status reviews. The auto-scheduler gives planners a constraint-based starting point using dates, estimates, capacity, velocity, and dependencies.
Decision supported
Whether the current plan is structurally possible, and what a more realistic delivery sequence would look like.
Planning lever: Safe draft space
#### The planning workshop needs safe working space
In a leadership workshop, teams can test changes without immediately disrupting Jira. Draft changes let the group explore, compare, and commit only the decisions that are ready.
Decision supported
Which changes are approved, which require more analysis, and which should remain in a scenario.
PMO, agile, and project management fit
### Use Plans when coordination problems affect delivery.
The value is clearest when a missed dependency, overcommitted team, or unrealistic date could create leadership escalations, delivery delays, or repeated replanning.
PMO portfolio and program visibility + Real situation
The CIO asks why a strategic initiative is marked green when two dependent teams have not started their work.
Plans response
Show the cross-space plan, dependency path, team assignments, and timing gap in one view so the discussion can focus on the decision needed.
Planning question
Which initiatives need a decision this week because capacity, dependencies, missing dates, or unassigned teams put the target outcome at risk?
Agile release and PI planning + Real situation
Four teams leave planning confident, but two teams are depending on the same integration work in the same sprint.
Plans response
Use the Program board and dependency view to expose the conflict before team-level plans create conflicts in the program plan.
Planning question
Which commitments appear manageable at the team level but create risk when dependencies and shared capacity are reviewed together?
Traditional project schedule coordination + Real situation
A project manager needs a milestone plan for stakeholders, but the actual work lives in Jira across multiple teams.
Plans response
Use dates, hierarchy, dependencies, and team assignments to build a planning view that stays connected to the Jira items people update.
Review prompt
Which milestones move if the integration epic slips by two weeks, and what work becomes blocked?
Sustainable capacity management + Real situation
A leadership team approves every priority, then discovers the same engineering group is assigned to all of them.
Plans response
Use capacity views and scenarios to make overload visible, then move the conversation to sequence, scope, or staffing decisions.
Review prompt
Which team is carrying the highest load in the next planning window, and what lower-priority work can shift?
Executive and stakeholder communication + Real situation
A steering committee wants a clear update, but the project has changed since the last slide deck was prepared.
Plans response
Use saved views and summaries to discuss current work, current risks, and decisions needed, without rebuilding the update from scratch.
Review prompt
What changed since the last review, what decisions are needed, and which risks affect the target date?
A useful plan shows whether the schedule, scope, capacity, dependencies, and leadership priorities can work together.
Capability to need map
### Start with the management problem, then choose the Plans capability.
Start with the decision leaders need to make, then choose the planning view that shows the right schedule, capacity, scope, and dependency information.
Leadership problem The portfolio review is full of status updates, but nobody can see how the work connects. Plans capability Cross-space plan using multiple work sources, hierarchy, saved views, and summary information. Decision it supports Which initiatives need attention, which risks matter, and where leadership should intervene. Leadership problem A sponsor wants a date change, but the impact is not clear enough to approve. Plans capability Scenarios and draft changes before saving selected edits back to Jira. Decision it supports Whether to accept the date, reduce scope, add capacity, or keep the current commitment. Leadership problem The roadmap assumes more team capacity than the organization actually has. Plans capability Capacity and velocity signals, sprint planning context, and auto-scheduler constraints. Decision it supports Which work moves, which scope shrinks, and which commitments need renegotiation. Leadership problem Individual teams report progress, but cross-team handoffs are blocking the overall delivery plan. Plans capability Dependency mapping, Program board dependency icons, off-track warnings, and timeline warnings. Decision it supports Which dependency gets escalated, resequenced, split, or assigned clearer ownership. Practical rule: use Timeline for timing, Program board for upcoming cross-team planning, Scenarios for what-if choices, Capacity for fit, Dependencies for sequence, and Summary for stakeholder discussion.
Interactive planning coach
### Match the planning challenge to the right Jira Plans move.
This interactive guide helps PMOs, project managers, scrum masters, and agile coaches decide how to use Jira Plans in common planning moments.
Before selecting an action, decide what kind of uncertainty is driving the planning conversation: timing, capacity, dependency, scope, or stakeholder confidence.
A target release date may change A shared team is over capacity Dependencies are blocking progress Executives need a trustworthy status view Recommended Plans move
#### Create a release planning scenario
Use a scenario to evaluate the proposed date change before committing updates. Compare the current plan with the proposed release plan and identify affected work, team load, and dependency impact.
- Duplicate the current plan into a scenario.
- Adjust the target release or date range.
- Review affected dependencies, capacity, and unsaved changes before deciding what to save.
Capability fit Scenarios · Timeline · Dependencies PMO Agile teams Project managers Before using this checklist, judge whether the PMO needs better portfolio visibility, better decision support, or a cleaner bridge between strategy and delivery.
#### PMO readiness: make the plan a decision surface.
A PMO gets the most from Jira Plans when roadmap discussion includes capacity, dependency, and sequencing evidence from live Jira work.
✓ Programs or initiatives can be traced to Jira work items. ✓ Leadership reviews include dependency and capacity risk, not only dates. ✓ Scenario changes are reviewed before they are saved back to Jira. 33% Readiness increases as the PMO uses Plans for tradeoff decisions, not just roadmap display.
Before using this checklist, judge whether the team needs better release confidence, better dependency visibility, or better capacity discipline.
#### Agile team readiness: review commitments before the sprint or PI is finalized.
Agile teams get value when Plans supports release planning, PI planning, cross-team dependency review, and sustainable capacity conversations.
✓ Team work is estimated enough to support capacity review. ✓ Cross-team dependencies are linked and reviewed before commitments are made. ✓ Release and sprint planning include sequence, not just scope. 33% Readiness increases when planning conversations make overload, blockers, and sequence visible early.
Before using this checklist, judge whether project control depends most on schedule, dependencies,

[truncated — full text at https://endash.us/toolkit/items/getting-started-with-atlassian-plans-for-pmo-and-vmo-leaders]

---

# Getting Started With Rovo For Agile Teams and PMOs

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/getting-started-with-rovo-for-agile-and-lean-teams-and-pmos
- **Tags**: jira, tooling, product, project, projectmanagement, pmo, vmo, scrum, planning, atlassian

Skip to main content Start Capabilities Agile uses Need map Practice map Adoption Atlassian Rovo for Jira and Confluence users
## Rovo for the way agile teams already work.
A practical introduction to Atlassian Rovo for PMOs, agile coaches, scrum masters, product owners, and delivery teams using Jira and Confluence every day.
Backlog clarity Epic slicing Team context Flow signals Search Find work context across Jira, Confluence, and connected tools without starting from a folder, page tree, or issue filter.
Chat Ask natural language questions about projects, pages, issues, blockers, decisions, and team knowledge.
Agents Use configurable AI teammates to help summarize, draft, organize, analyze, and move work forward.
Studio Create more tailored agent workflows for repeated patterns such as intake review, sprint preparation, or change impact analysis.
What Rovo adds
### From static systems of record to useful systems of work.
Most agile teams already have the artifacts: Jira issues, Confluence pages, meeting notes, product briefs, decision records, diagrams, and retrospectives. Rovo helps teams turn that material into shared understanding when work is planned, refined, reviewed, or improved.
The Rovo operating layer
#### Three capabilities create the foundation.
Search, Chat, and Agents are the starting points for practical adoption. They help teams move from hunting for information, to asking better questions, to making recurring agile routines easier to run.
Find context Understand work Repeat the routine 01 S
#### Search finds the missing context
Use Rovo Search when the team needs the source material behind a Jira item: a Confluence decision record, intake note, product brief, dependency discussion, meeting recap, or related issue.
Why it mattersAgile decisions improve when teams can quickly trace the work back to the reason it exists. Discovery Onboarding Decision recall 02 C
#### Chat turns context into answers
Use Rovo Chat when the user knows the question but does not know where the answer lives. Ask about blockers, scope changes, open questions, duplicated work, or the current state of an initiative.
Why it mattersTeams spend less time navigating tools and more time clarifying tradeoffs, risks, and next actions. What changed? What is blocked? What needs review? 03 A
#### Agents support repeatable team routines
Use Rovo Agents when the team repeats the same pattern often: sprint summary, refinement check, release note draft, decision log update, status narrative, or intake triage.
Why it mattersCommon agile ceremonies get better inputs without forcing people to rebuild the same summary every time. Summarize Draft Analyze Jira plus Chat
#### Backlog health scan
Before refinement, ask Rovo to inspect a candidate set of issues and identify stale items, missing acceptance criteria, unclear users, duplicate requests, oversized stories, and dependency-heavy work.
Example prompt
Review the issues in [refinement filter name]. Group them into ready, needs clarification, likely duplicate, too large, and blocked by dependency. Explain what should be fixed before the refinement session.
Confluence plus Search
#### Decision trace for a planned epic
When an epic has vague scope, use Rovo to find related Confluence pages, decision records, meeting notes, prior Jira issues, and linked artifacts so the team can see the intent behind the work.
Example prompt
Find the decisions, product notes, and related Jira issues that explain why [epic name] exists. Summarize the goal, known constraints, open questions, and likely dependencies.
Agent
#### Sprint review prep
Create an agent-assisted routine that summarizes completed work, carried-over items, notable scope changes, unresolved blockers, and open follow-ups from Jira and Confluence.
Example prompt
Prepare a sprint review brief for [team name]. Include completed outcomes, unfinished work, customer or stakeholder value, blockers, and follow-up decisions that need attention.
Studio
#### Reusable intake triage
Use Studio for a repeatable intake workflow that checks whether new requests have a clear problem, requester, business value, urgency, dependency notes, and the right target project.
Example prompt
Evaluate this new request against our intake criteria. Identify missing information, likely owner, related work, risk level, and whether it should become an epic, story, spike, or decision record.
Agile and lean fit
### Rovo is most valuable when it supports the habits teams already need.
For regular Jira and Confluence users, Rovo earns attention when it improves flow, quality, transparency, and learning in the work people already do.
Keep the backlog refinement-ready + Common challenge
Backlogs grow faster than teams can clarify them. Items become stale, duplicate, too large, or disconnected from product goals.
Rovo assist
Ask Rovo to summarize stale issues, group similar requests, surface missing acceptance criteria, or compare a story against related Confluence product context.
A useful pattern: before refinement, use Rovo to identify stories that need clearer intent, smaller slices, current dependencies, or better links to source decisions.
Try this in practice
Look at [project key] issues planned for the next refinement session. Which items are missing acceptance criteria, have unclear user value, appear stale, or need supporting Confluence context?
Decompose epics into deliverable slices + Common challenge
Large epics hide uncertainty. Teams discuss the same work repeatedly because outcomes, users, constraints, and release slices are not visible.
Rovo assist
Use Rovo to summarize an epic, pull relevant Confluence context, draft candidate stories, identify open questions, and highlight dependencies.
The useful outcome is a better starting point for human slicing and planning.
Try this in practice
For [epic name], summarize the intended outcome, known users, constraints, dependencies, and unanswered questions. Then propose story slices by user value and delivery risk.
Improve flow and delivery metrics + Common challenge
Metrics are often collected, but not translated into operational learning. A dashboard says work is stuck. The team still has to find out why.
Rovo assist
Ask questions about bottlenecks, aging work, blocked items, repeated rework, and sprint carryover. Connect Jira patterns to Confluence decisions or meeting notes.
Rovo can help move the conversation from reporting the number to investigating the system condition behind the number.
Try this in practice
Review issues completed, carried over, blocked, or reopened in [sprint name]. What patterns suggest queue buildup, unclear acceptance criteria, handoff delays, or dependency problems?
Turn Confluence into usable team memory + Common challenge
Confluence contains important context, but pages age unevenly. Teams may not know which decision record, requirement, or retrospective is relevant today.
Rovo assist
Use Rovo to find, compare, summarize, and draft from Confluence context while staying inside everyday planning and delivery routines.
This helps PMOs and agile coaches reduce knowledge debt: the hidden cost of decisions, definitions, and agreements that exist but are hard to use.
Try this in practice
Find the most relevant pages and Jira issues for [initiative name]. Identify conflicting information, outdated assumptions, and pages that should be updated or archived.
Make retrospectives more evidence-based + Common challenge
Retrospectives can become anecdotal when teams rely only on what people remember from the last sprint.
Rovo assist
Ask Rovo to summarize sprint changes, blockers, carryover, decision points, and recurring friction from Jira and Confluence context.
The strongest use is bringing better evidence into the team conversation.
Try this in practice
Prepare retro evidence from [sprint name]. Summarize blockers, carryover, reopened work, decision delays, and recurring friction. Keep the output factual and link back to source items.
Rovo should help agile teams see the work, understand the system, and make better decisions sooner.
Capability to need map
### Choose the Rovo pattern based on the team problem.
Rovo is easier to adopt when each capability is tied to a familiar agile or lean need. This map gives PMOs and agile coaches a practical way to explain when a team should use Search, Chat, Agents, or Studio.
Team need A product owner is refining a messy backlog before sprint planning. Rovo capability Chat over Jira issues, with Search for related Confluence context. Useful output Ready or not-ready grouping, missing details, duplicates, stale items, and dependency notes. Team need A delivery lead needs a status narrative that reflects actual work. Rovo capability Agent-assisted summary from Jira activity, blocked items, carryover, and related pages. Useful output Concise status brief with outcomes, risks, blockers, decisions needed, and source links. Team need An agile coach wants better evidence for a retrospective. Rovo capability Chat questions across sprint issues, comments, status transitions, and Confluence notes. Useful output Patterns in aging work, rework, blocked flow, unclear acceptance criteria, and delayed decisions. Team need A PMO wants consistent intake without slowing teams down. Rovo capability Studio-built intake agent with agreed evaluation criteria. Useful output Missing information, likely routing, related work, risk level, and recommended next action. Practical rule: use Search when the problem is finding context, Chat when the problem is understanding context, Agents when the pattern repeats, and Studio when the organization needs a consistent reusable workflow.
Interactive practice map
### Start with the agile problem, then choose the Rovo capability.
This map shows how a regular Jira or Confluence user can match common delivery challenges to functional Rovo patterns, with example outputs that are useful in backlog refinement, planning, review, and improvement conversations.
Before selecting an action, decide which team problem is most visible right now: unclear work, hidden context, slow flow, weak signals, or knowledge debt.
Backlog items are unclear or stale An epic is too large to plan confidently Sprint metrics show friction, but the cause is unclear Important decisions are scattered across pages and issues Recommended Rovo pattern
#### Refinement readiness review
Use Rovo to review candidate backlog items before refinement. Ask for missing acceptance criteria, unclear user value, outdated links, duplicate items, and dependencies that should be visible before the team discusses sizing or sequencing.
- Start from a Jira filter or sprint candidate list.
- Ask Rovo to identify items that need clarification.
- Use the output as a facilitation aid, not as the final backlog decision.
Capability fit Search · Chat · Agents PMO Agile coach Team user Before using this checklist, judge whether the PMO needs better reporting, better governance, or better delivery learning. Rovo helps most when the use case is clear.
#### PMO use pattern: turn portfolio evidence into clearer conversations.
Use Rovo to summarize delivery status from Jira, connect risks to Confluence decisions, and prepare review prompts that help leaders ask better questions about flow, value, and dependencies.
✓ Portfolio review starts from current Jira delivery signals. ✓ Risks are connected to documented decisions or unresolved questions. ✓ Status conversations distinguish output, flow, and outcome evidence. 33% Readiness increases as governance routines use real work evidence rather than disconnected status narratives.
Before using this checklist, judge which coaching moment matters most: refinement, planning, daily flow, review, or retrospective.
#### Agile coach use pattern: make team conversations more evidence-based.
Use Rovo to bring relevant Jira patterns, Confluence decisions, and sprint evidence into coaching conversations without turning the session into dashboard review.
✓ The team can see where work is aging, blocked, or repeatedly carried over. ✓ Retro inputs include evidence from Jira and Confluence, not memory alone. ✓ Improvement actions are linked to observable system conditions. 33% Readiness increases when Rovo supports better faci

[truncated — full text at https://endash.us/toolkit/items/getting-started-with-rovo-for-agile-and-lean-teams-and-pmos]

---

# Luck Exposure

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/luck-exposure-scroll
- **Tags**: focus, career, culture, collaboration, scaling, goals, outcomes

A Philosophy of Fortune
## Luck Exposure
Luck isn't scarce — it saturates the world. The question is how much of it you're in the path of.
explore the concept The Idea
### Not all luck is accidental.
In finance, risk exposure measures how much capital sits in the path of uncertainty. Luck Exposure is the same logic, inverted — instead of limiting exposure to protect against loss, you maximise it to multiply the chances of gain.
Every cold email, side project, conversation at a party, or creative work released into the world is a seed. You can't know in advance which will take root. But you can decide how many you plant — and that changes everything.
And luck compounds. Each fortunate outcome opens doors, introduces people, and creates conditions where more luck becomes possible. One bloom scatters seeds of its own. The field you tend today grows next season without you.
"Luck is not a quantity. It's a probability field — one you walk through, and one that grows larger the longer you walk." Risk vs. Luck Exposure Risk Exposure Quantifies how much capital is subject to potential loss. The goal is to minimise it — protecting value from uncertain downside.
Luck Exposure Quantifies how many seeds are planted across opportunity space. The goal is to maximise it — multiplying chances of uncertain upside.
The Laws
### How Luck Exposure Works
Three laws. One strategy.
01
#### Luck Exists Everywhere
Every moment, interaction, and action holds the potential for an unexpected fortunate outcome. The world isn't stingy with luck — it's ambient, always present, waiting to be encountered by someone who shows up.
02
#### No Seed Blooms on Command
You plant with intention — but luck decides the harvest. The project you poured yourself into may lie dormant. The offhand connection you almost didn't make may change everything. Which seeds bloom was never yours to control. Only the planting is.
03
#### Luck Compounds
Every fortunate outcome creates conditions for more. The introduction leads to a job leads to a collaboration leads to an opportunity nobody could have planned. Volume gets you to the first bloom — but it's the compounding that builds the garden. The longer you plant, the more it grows without you.
Interactive Garden
### Move Through the Garden. Watch Luck Compound.
Hover across the canvas to plant seeds — lucky blooms scatter new seeds of their own.
0 Seeds Planted 0 Lucky Events — Observed Rate ◆ each stem is a seed · ✦ golden blooms are lucky events · each bloom scatters new seeds — luck compounds
Luck Surface Area Real World Seeds
### Every Domain Has a Garden
The strategy looks different everywhere — the logic is always the same.
Career
##### Apply broadly, not perfectly
The job that shapes your trajectory is rarely the one you spent three weeks perfecting an application for. Send 50 thoughtful applications. One will open a door you didn't even see.
Creativity
##### Ship more, agonise less
Most creative breakthroughs arrive at piece 47, not piece 2 — when you've stopped performing brilliance and started just making things. Volume is what gets you there.
Relationships
##### Say yes more often
The mentor who changed your life, the collaborator who made you sharper, the person you married — none of them appeared at a moment you had planned for. You just happened to be there.
Business
##### Run more experiments
The product line that defines a company is almost never the planned one. It's the experiment someone ran on a slow Tuesday — the seed nobody expected to bloom.
"You can't force luck — but you can be in more places for it to find you."
Luck Exposure is not magical thinking. It's a discipline. It asks you to act before certainty arrives, reach before you're ready, and plant in soil you've never tested. Not every seed will bloom. Most won't. But each one that does scatters seeds of its own — and luck, once you've invited it in, has a way of compounding.
Go plant some seeds LuckExposureThe more seeds you plant, the luckier you get.

---

# Mini Shai-Halud

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/mini-shai-halud
- **Tags**: ai, development, governance, dependency, guide, design, project, machineLearning

Skip to main content
- Threat
- Spread
- Detect
- Prevent
- History
- Resources
LT DK 170+ Active campaign Field Guide · v1.0 For npm and PyPI defenders
## When the worm wears a trusted signature .
On May 11, 2026, a self-propagating worm dubbed Mini Shai-Hulud compromised 84 npm artifacts across 42 @tanstack/* packages in six minutes. Within forty-eight hours the campaign had reached 172 packages across npm and PyPI, totalling more than half a billion cumulative downloads. Every malicious version carried a valid SLSA Build Level 3 provenance attestation. The signatures were genuine. The code was not. This is how it worked, how to know if you were caught, and what to do next.
172 Packages hit 403 Malicious versions 518M Weekly download reach 6 min From publish to detection What it is
### An identity attack dressed as a trusted release.
Mini Shai-Hulud is not a typosquat and it is not a hijacked maintainer account. It is a worm that hijacks the release pipeline itself, mints a short-lived publish token through the project's own OIDC binding, and ships a malicious version that the registry, the signer, and every downstream verifier all consider perfectly legitimate.
#### The class of attack
A software supply-chain worm: malware that uses the credentials it steals to infect more packages, which infect more developers, which yield more credentials. The propagation is automatic. No human attacker is in the loop after the initial foothold.
The "Mini" in the name refers to a TeamPCP variant first observed in April 2026 against SAP CAP packages. The May wave is its fifth and largest run since the original Shai-Hulud worm appeared in September 2025.
#### Why it matters
The compromised packages include @tanstack/react-router , which receives approximately 12 million weekly downloads. Other named victims include @uipath/* , @mistralai/* , @opensearch-project/* , and the Guardrails AI PyPI package.
CVE-2026-45321 was issued at CVSS 9.6. The TanStack family is the documented index case, but the worm spreads to anyone whose CI/CD secrets it can reach.
#### The three-link chain
01 · Pwn Request
##### A fork opens a draft PR
The TanStack bundle-size workflow ran on pull_request_target for fork PRs and checked out the fork's merge ref. Attacker code ran with the base repo's trust.
02 · Cache Wedge
##### Poison crosses the boundary
Attacker code wrote a malicious pnpm store into the GitHub Actions cache. When maintainer PRs were merged to main, the release workflow restored the poisoned cache.
03 · Memory Read
##### OIDC token leaves the runner
Attacker binaries read the runner's /proc/<pid>/mem and extracted the OIDC token. The token was used to mint a short-lived npm publish credential through trusted publishing.
04 · Signed Ship
##### Sigstore attests honestly
The build pipeline really did run inside tanstack/router on refs/heads/main . The attestation is correct. SLSA proves provenance, not authorisation.
The attacker did not invent novel tradecraft. They recombined published research. — TanStack postmortem, May 12 2026 Threat actor
##### TeamPCP
Also tracked as DeadCatx3, PCPcat, ShellForce, CipherForce. Attributed by StepSecurity and Wiz with high confidence based on toolchain reuse from the SAP CAP, Bitwarden CLI, Lightning, Intercom and Trivy compromises.
Payload
##### 2.3 MB obfuscated stealer
A file named router_init.js with daemonisation, ten parallel credential-collection classes, and eleven AES-256-GCM encrypted sub-payloads decrypted only by the Bun runtime.
Exfiltration
##### Three redundant channels
The Session decentralised messenger network, GitHub dead-drop repositories, and a typosquat domain git-tanstack[.]com . There is no attacker-controlled C2 to block by IP.
How it spreads
### One compromised maintainer becomes a hundred.
A worm earns the name when it spreads without a human in the loop. Once Mini Shai-Hulud lands on a developer machine or a CI/CD runner, it looks at what the victim has the keys to and uses those keys to infect the next set of packages.
#### The propagation loop
#### What the worm steals
GitHub Actions OIDC tokens, GitLab and CircleCI runner tokens, AWS IMDSv2 role credentials ( 169.254.169.254 ), ECS/Fargate task metadata ( 169.254.170.2 ), GCP and Azure metadata, Kubernetes service accounts, HashiCorp Vault tokens on 127.0.0.1:8200 , npm and package-registry tokens, cryptocurrency wallets, password managers including 1Password and Bitwarden vault data, and credentials for messaging and AI tooling.
#### Where it hides
Persistence is dropped into ~/.claude/settings.json as a SessionStart hook, ~/.vscode/tasks.json as a folderOpen task, and ~/.claude/router_runtime.js as the staged payload. On macOS a LaunchAgent named com.user.gh-token-monitor polls GitHub every sixty seconds. On Linux the equivalent runs under systemd.
##### The dead-man switch
The gh-token-monitor daemon polls GitHub with the stolen token. If it receives an HTTP 40x indicating the token was revoked, it attempts to execute rm -rf ~/ on the host. The switch has a 24-hour TTL and exits cleanly afterwards, but if you act within that window you must disable persistence before rotating any tokens.
Are you compromised?
### The first hour matters more than the next ten.
If you installed any affected package between 2026-05-11 19:20 UTC and the deprecation window two to three hours later, treat the install host as compromised. The order of operations below is the consensus guidance from TanStack, StepSecurity, Snyk, Wiz, and Endor Labs.
##### Before you do anything else
Do not revoke npm or GitHub tokens before you have either disabled the dead-man switch or isolated and imaged the affected machine. The destructive handler is the first thing to neutralise.
#### Step 1 — Look for the payload on disk
/dev/null">Copy # The 2.3 MB payload is the fastest single check. $ find . -name 'router_init.js' -size +1M 2>/dev/null /dev/null">Copy # The orphan-commit SHA from optionalDependencies is a clean signal. $ grep -r '79ac49eedf774dd4b0cfa308722bc463cfe5885c' \ package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null /dev/null">Copy # Persistence artefacts in user tooling directories. $ ls -la ~/.claude/settings.json \ ~/.claude/router_runtime.js \ ~/.vscode/tasks.json 2>/dev/null Copy # Disable the dead-man switch before anything else. $ launchctl list | grep gh-token-monitor # macOS $ systemctl --user list-units | grep gh-token-monitor # Linux
#### Step 2 — Check your GitHub footprint
Copy # Stolen-credential dead-drop repos use this exact description. $ gh search repos --owner @me 'Shai-Hulud: Here We Go Again' Copy # The worm authors dead-drop commits as claude@users.noreply.github.com. $ gh search commits \ --author 'claude@users.noreply.github.com' \ --owner @me
#### Step 3 — Run the interactive triage
Before you click, ask yourself honestly: when did your build last run, and would you know if a fresh tarball had been pulled into it? The questions below take thirty seconds.
Q1 Did your CI or any developer machine run npm install against an affected scope between 2026-05-11 19:20 UTC and 2026-05-12 02:00 UTC? Yes, or unsure Confirmed no Q2 Do your lockfiles pin integrity hashes for the affected packages, with hash verification enforced in CI? Yes, with mismatch blocking No, or partially Q3 Have you searched the affected hosts for router_init.js larger than 1 MB? Searched, nothing found Found a match Not yet searched Start over
#### Indicators of compromise
Type | Indicator
File | router_init.js — 2.3 MB obfuscated payload, sometimes renamed router_runtime.js
File | setup.mjs — Bun installer dropped under ~/.claude/ or ~/.vscode/
Persistence | ~/.claude/settings.json with a SessionStart hook re-executing the payload
Persistence | ~/.vscode/tasks.json with a folderOpen task pointing at setup.mjs
Persistence | ~/Library/LaunchAgents/com.user.gh-token-monitor.plist (macOS) or equivalent systemd unit (Linux)
SHA | 79ac49eedf774dd4b0cfa308722bc463cfe5885c — orphan commit referenced by optionalDependencies
String | Shai-Hulud: Here We Go Again — description on public GitHub dead-drop repositories
String | A Mini Shai-Hulud has Appeared — description on worm-marker repositories
Commit author | claude@users.noreply.github.com on dead-drop commits
Branch name | Dune universe terms: atreides , fremen , harkonnen , melange , sietch , sardaukar , stillsuit , thumper , and others
Network | filev2[.]getsession[.]org , seed1[.]getsession[.]org – seed3[.]getsession[.]org
Network | git-tanstack[.]com (typosquat), api[.]masscan[.]cloud , 83[.]142[.]209[.]194
CVE | CVE-2026-45321 , CVSS 9.6, GHSA-g7cv-rxg3-hmpx
If any of these turn up, isolate the host, image it forensically, then rotate credentials in this order: npm tokens, GitHub personal access tokens, cloud keys (AWS, GCP, Azure), Vault tokens, Kubernetes service accounts, SSH keys.
Prevention
### The control that closes each gap.
Provenance attestations and trusted publishing are still better than long-lived static tokens. Endor Labs' Peyton Kennedy put it bluntly to VentureBeat: the actual control that matters here is OIDC scope, not provenance and not 2FA. The checklist below works through the six gaps Mini Shai-Hulud exploited.
0 /9 controls
##### Pin id-token: write to the publish job only OIDC
Set permissions: id-token: none at the workflow root and grant id-token: write only in the specific job that publishes. Trusted-publisher bindings should pin the workflow filename and the branch refs/heads/main .
##### Enforce lockfile integrity in CI SRI
Use Subresource Integrity or lockfile hash verification with pinned integrity fields for every dependency. Any version with a hash mismatch should block the build. This breaks the worm's quiet republish loop.
##### Set a minimum release age in every package manager Cooldown
Most malicious versions are detected and yanked within hours of publication. A three-day cooldown closes the smash-and-grab window entirely. Configure in .npmrc , pnpm-workspace.yaml , .yarnrc.yml , bunfig.toml , and uv.toml — copy-paste configs are in the panel below.
##### Remove pull_request_target from build workflows Trigger
The trigger is fine for labelling and comments. It is dangerous wherever it checks out the fork's merge ref and runs build commands. Use pull_request with a separate, scope-limited automation workflow.
##### Stop trusting the GitHub Actions cache across boundaries Cache
Treat the Actions cache as untrusted input when it is reachable from fork-triggered runs. Either disable cache restoration in release workflows or scope cache keys so the publish path can never restore a fork-poisoned blob.
##### Disable lifecycle scripts in CI by default npm
Run npm ci --ignore-scripts wherever practical. The payload depends on preinstall and prepare hooks; ignoring them removes the foothold even when a poisoned tarball reaches the runner.
##### Monitor for optionalDependencies referencing orphan commits Provenance
A reference to a SHA that is not on any branch is the smoking gun in this campaign. Provenance attestations remain a necessary signal — they are not a sufficient one. Treat them as part of the picture, not the whole picture.
##### Use ephemeral, short-lived secrets in build runners Identity
If the payload reads runner process memory and the only thing in memory is a token that expires in five minutes with narrow scope, the blast radius is small. Long-lived PATs and broad cloud admin roles on shared runners are the actual prize.
##### Subscribe to a feed and rehearse the response Process
Wire Socket, Snyk, StepSecurity or your registry's own advisory feed into your build alerts. Rehearse the order of operations: isolate first, disable persistence, image, then rotate. The dead-man switch makes muscle memory matter.
#### Minimum release age — copy-paste configs
Mini Shai-Hulud was detected six minutes after publish, and the affected versions were deprecated within hours. A three-day minimum-age policy in your package manager would have made every affected version unreachable. Each manager calls the feature something different and measures time in a different unit; the five configs below all enforce the same three-day cooldown.
npm pnpm Yarn Bun uv (Python) File ~/.npmrc &middot; npm 11.10.0+ &middot; unit:

[truncated — full text at https://endash.us/toolkit/items/mini-shai-halud]

---

# Minimum Viable Change MVC

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/minimum-viable-change-mvc
- **Tags**: management, focus, teamwork, agile, scaling, delivery, scrum, kaizen, continuousimprovement, outcomes, leadership, projectmanagement, planning

Context
- Why
- Trap
- Framework
- Benefits
The loop
- Outcome
- Constraint
- Intervention
- Readout
Practice
- Avoid
- Patterns
- Scaling
- Start
En Dash Consulting
## Minimum Viable Change
A practical framework for transformation that treats change like product discovery—start small, learn fast, and compound results over time.
⚠️
### Why Transformations Fail
Multiple consulting firms report similar transformation failure rates, though the exact numbers vary. The consistency of poor outcomes points to systemic problems in how organizations approach change.
70-88% Fail to Meet Goals 48% Miss Outcome Targets 30% Meet Timeline/Budget
#### The Pattern
These numbers reflect a fundamental mismatch between how transformation programs operate and how organizational change actually happens. Large-scale initiatives create coordination overhead, slow learning cycles, and late discovery of critical constraints.
The result: organizations invest heavily in planning and governance while teams struggle to deliver meaningful change.
##### Check Understanding
A company launches a comprehensive transformation program covering culture, processes, and technology across all departments. Based on research data, what's the likely outcome?
High probability of success due to comprehensive scope High probability of failure due to coordination complexity and slow learning Neutral outcome—scope doesn't correlate with success rates What's the primary cause of transformation failure according to the pattern described?
Insufficient budget allocation Lack of executive commitment Slow learning cycles and late constraint discovery 🚧
### The Big Program Trap
#### What Typically Happens
- Commit to a big plan early: Detailed roadmaps and timelines established before reality testing
- Discover reality late: Critical constraints surface months into execution
- Add governance to manage uncertainty: Steering committees, status reports, dependency tracking
- Teams pay the tax: More time in coordination meetings and rework than actual delivery
#### The Result
More coordination than deliveryPrograms become self-perpetuating bureaucracies. Status reporting consumes more effort than the work being reported on.
More reporting than learningTeams spend energy justifying variance from the plan rather than adapting based on what they learn.
Productivity, culture, and customer satisfaction often decline during transformation programs—the opposite of intended outcomes.
##### Check Understanding
A transformation program establishes a detailed 18-month roadmap with dependencies mapped across 12 teams. Three months in, teams discover a critical technical constraint. What typically happens?
Teams quickly adapt the plan based on new learning Governance layer added to manage the variance, slowing delivery further Program pauses to replanning from scratch 🔄
### Minimum Viable Change Framework
#### Treat Change Like Product Discovery
Apply product thinking to organizational change: hypothesize, test, learn, repeat. The goal is not to minimize change itself but to minimize the batch size of change experiments.
#### The Point of "Minimum"
- Reduce risk: Small experiments limit downside exposure
- Reduce coordination cost: Changes contained within teams avoid dependency overhead
- Increase learning speed: Faster feedback loops surface what works and what doesn't
#### A Useful Litmus Test
If it needs a steering committee to start, it isn't minimumChanges requiring extensive approval processes and cross-functional alignment before beginning are too large. Make it smaller.
#### The MVC Loop
One outcome, one bottleneck, one small bet, two-week readout
Desired Outcome Pick one measurable outcome Constraint Find where work waits Smallest Intervention One lever per experiment Quick Readout Decide: adopt, adapt, abandon
##### Check Understanding
A team wants to improve their deployment process. Which approach best exemplifies Minimum Viable Change?
Implement a complete CI/CD pipeline with automated testing, deployment, and monitoring across all services Add one automated test gate to the deployment of their highest-risk service Create a six-month roadmap for DevOps transformation pending steering committee approval Why does MVC emphasize reducing coordination cost?
To minimize meetings and save time To increase learning speed by removing dependency overhead To avoid involving leadership in decisions 📈
### Why Small Changes Win
#### Short Feedback Loops
Small changes complete quickly, generating learning within days or weeks instead of months. This enables:
- Less rework: Course-correct before significant effort is invested
- Better alignment: Teams stay synchronized with actual constraints rather than planned assumptions
- Lower risk: Failures are contained and cheap
#### Constraint Economics
Systems improve by addressing bottlenecks, not by optimizing everything simultaneously.
Fix the bottleneck and throughput risesFocused improvement on the constraint increases system capacity immediately.
Try to fix everything? Nothing movesDistributed effort across many improvements dilutes impact and creates coordination overhead.
#### Compounding
Small friction removed returns time every day. A five-minute improvement to a daily process yields 1,825 minutes per year per team member—over 30 hours of reclaimed capacity.
Multiple small improvements compound. Ten friction-reducing changes create exponentially more value than one large initiative that arrives months later—if it arrives at all.
##### Check Understanding
A team identifies five process improvements, each saving 3 minutes daily. Should they implement all five simultaneously or sequentially?
All five simultaneously—maximize time savings immediately Sequentially—test each change, learn from results, avoid coordination overhead Neither—3 minutes isn't worth the effort According to constraint economics, what happens if you optimize non-bottleneck processes?
System throughput increases proportionally System throughput remains unchanged—work still waits at the constraint Non-bottleneck improvements eventually eliminate the constraint 🎯
### Step 1: Pick One Outcome That Matters
#### Use "So That" Framing
Connect the metric to meaningful impact:
- "Reduce lead time so that customer feedback shows up in the same month"
- "Improve reliability so that releases stop being stressful events"
#### Good Outcomes Share Three Traits
- Visible within a few weeks at most: Long feedback loops prevent learning
- Owned by a team: Outcomes spanning multiple teams create coordination overhead
- Measurable without a data project: If measurement requires new infrastructure, the outcome is too complex
#### Outcome Menu (Choose One)
- Lead time / cycle time
- Time blocked / waiting
- Release frequency
- Incidents / escaped defects
- Time to restore service
- Percent of work with clear acceptance criteria
##### Check Understanding
Which outcome best fits MVC criteria?
"Improve customer satisfaction across all product lines over the next year" "Reduce code review wait time from 3 days to 1 day so that features ship faster" "Transform engineering culture to be more agile and innovative" A team proposes "reduce time to market by 40%" as their outcome. What's the primary issue?
The percentage target is too aggressive Missing the "so that" framing—unclear why this metric matters No issue—this is a well-formed outcome 🔍
### Step 2: Find the Constraint Fast
#### The Question
Where does work wait the longest, most often?
#### Last-5 Method
- Take the last 5 finished items
- For each, mark the longest wait
- Tally the winner
- Name it as a hypothesis: "We stall at [review / QA / approval / dependency / intake]"
This takes 15 minutes. Precision isn't required—you're identifying the most obvious bottleneck, not conducting a comprehensive analysis.
#### Common Bottlenecks
- Approval queue: Work waiting for stakeholder sign-off
- Review pile-up: Code or design reviews queued behind other work
- QA as a phase: Testing treated as a handoff rather than continuous activity
- External dependency drag: Waiting on another team's delivery
- Intake churn: "Not ready" work entering the system anyway
- Environment/build/test delays: Infrastructure friction blocking progress
##### Check Understanding
Using the Last-5 method, a team finds: 3 items waited longest at code review, 1 at QA, 1 at deployment. What's the constraint?
Code review—it's the most frequent bottleneck All three stages equally—address them simultaneously Unclear—need more data before deciding A team wants to conduct a thorough two-week analysis mapping all dependencies and wait states across their entire value stream. What's the problem with this approach?
No problem—comprehensive analysis produces better results Violates MVC principles—two weeks of analysis delays learning from actual experiments Two weeks is insufficient—needs at least a month ⚡
### Step 3: Choose the Smallest Intervention
#### Three Levers (Pick One)
##### Lever A: Reduce WIP
- Add a WIP limit only where the pile-up is worst
- Stop-start rule: finish something before starting the next
- Swarm rule: blocked > 1 day triggers help
##### Lever B: Simplify a Handoff
- Replace an approval meeting with a checklist + 24-hour SLA
- Pair QA with dev for the top 1 item/day
- Refine entrance/exit criteria to ensure only ready work enters
##### Lever C: Shorten the Feedback Loop
- Daily 10-minute "blockers + next test" standup
- Weekly demo to real stakeholders (not a status update)
- One "definition of done" gate that prevents rework
#### MVC Candidate Test (Before Choosing)
Pass/fail checklist—is the change:
- Reversible within 2 weeks?
- Local to one team?
- Low coordination cost?
- No reorg required?
- Visible with chosen metric in the short timeframe?
If it fails: Make it smaller until it passes.
##### Check Understanding
Code review is the constraint. Which intervention best fits MVC criteria?
Implement automated code analysis, restructure review assignments, and train all engineers on review best practices Require two reviewers instead of three for PRs under 200 lines Hire three additional senior engineers to handle review load A proposed change requires sign-off from three VPs before starting. What does this signal?
The change is appropriately scoped given its importance The change is too large—fails the "needs a steering committee" test Proceed once approvals are obtained 📊
### Step 4: Quick Readout and Decision Discipline
#### Write the Experiment Card Before Starting
Document these elements before execution:
- Outcome: [metric]
- Constraint: [where work waits]
- Change: [one lever]
- Timebox: 1-2 weeks
- Success threshold: [target]
- Owner: [role]
#### Decision Options
AdoptImprovement observed and no new brittleness introduced. Keep the change.
AdaptPartial improvement; tune one parameter and run another week.
AbandonNo movement on the metric. Stop and pick a different small bet.
Avoid the temptation to continue experiments that aren't working. The value of MVC is fast learning—which requires killing failed experiments quickly.
##### Check Understanding
After one week, an experiment shows no improvement. The team believes it needs "just a bit more time." What's the correct decision?
Extend to two more weeks—initial timeboxes are guidelines Abandon—no signal of improvement means try a different intervention Adapt—add a second change to accelerate impact An experiment improves the metric by 15% but introduces new coordination overhead. What decision fits MVC principles?
Adopt—15% improvement justifies the overhead Adapt—keep the improvement, experiment with reducing the overhead Abandon—any new overhead is unacceptable 🚫
### Anti-Patterns That Make Small Change Useless
#### Bundling Changes
Implementing multiple changes simultaneously prevents causal learning. If three things change and the outcome improves, which change drove the result?
#### Measuring Activity Instead of Outcomes
Tracking "number of standups held" or "training sessions completed" misses the point. MVC focuses on outcome metrics like cycle time, defect rate, or throughput.
#### Tool-First "Because We Bought It"
Starting with a tool purchase and working backward to justify its use violates MVC principles. Tools should a

[truncated — full text at https://endash.us/toolkit/items/minimum-viable-change-mvc]

---

# Modal vs Modeless, an exploration

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/modal-vs-modeless-exploration-scroll
- **Tags**: focus, communication, ui, ux, design, development, product, guide

Skip to main content An En Dash Scroll on Accessible Design
## Modal vs Modeless
Two fundamental forces in interface design — one demands your attention, the other earns it. Understanding both is the first step to designing for everyone.
Begin the Journey ↓ Scroll to explore Preface
### Design is a conversation between a system and a human being.
Every button, every dialog, every floating panel — each one is a sentence in that conversation. How you structure that conversation determines whether people feel empowered or controlled, guided or lost, included or left behind.
Chapter 01 — Origin
### It all starts with a single word: Mode.
The terms modal and modeless come from the same root — "mode," meaning a state or condition that changes how something behaves.
A modal interface switches the application into a new mode. It changes what the system will respond to. It narrows the field of possibility until you act.
A modeless interface keeps all modes open simultaneously. The system stays fully alive around any interaction — nothing is locked away, no flow is interrupted.
This distinction — small in vocabulary, vast in consequence — shapes every digital experience you've ever had. And it shapes your users' experience of your work, too.
MODE Latin: modus · "measure, manner"
In music, a mode constrains which notes are available. In grammar, a mood constrains what a sentence can mean. In UI design, a mode constrains what actions a user can take — and when. Modal experiences interrupt. They say: "Stop. Answer this first." Modeless experiences coexist. They say: "Here's a tool. Use it whenever you're ready." Neither is inherently better. Both serve real purposes. The wisdom lies in knowing which to reach for — and why.
Chapter 02 — The Focused World
### Modal
"Stop. Pay attention. This matters."
A modal interface demands your full attention. It steps in front of everything else, puts the rest of the world on hold, and says: before we go any further, we need you here.
Think of the dialog box that appears when you're about to close an unsaved document. Or the login screen that blocks access to a protected area. Or the confirmation prompt before a permanent deletion. These are modal moments — and they serve real purposes.
Modal interfaces capture all keyboard and pointer input. They prevent interaction with the underlying application until the user responds. This is the point: some decisions genuinely need to be made before anything else can continue.
- Exclusive Focus Captures all input — keyboard, pointer, screen reader focus — until dismissed. Nothing else responds.
- Mandatory Interaction Users must respond — confirm, cancel, or input — before the primary workflow resumes.
- Workflow Interruption By design, the flow stops. Overused, this becomes frustrating. Used well, it prevents costly mistakes.
- Simpler State Management The application is in one defined state during modal interaction — simpler to build, test, and reason about.
Watch Out There's a critical difference between a purposeful modal — one that protects the user or requires essential input — and a disruptive pop-up that exists only to serve the system's interests, not the user's. Never confuse the two. One is good design. The other is manipulation. Try it: Live Demo
Document Editor — Unsaved Changes Close Document
##### Save before closing?
You have unsaved changes. If you close now, your work will be lost. This cannot be undone.
Cancel Discard Save Accessibility in Modals A well-built modal traps keyboard focus inside it and returns focus to the trigger on close. Screen readers announce role="dialog" and aria-modal="true" . The Escape key closes it. Skipping any of these makes the modal inaccessible. Chapter 03 — The Open World
### Modeless
"Here's your toolkit. Work your way."
A modeless interface trusts the user. It offers tools, information, and controls that stay present and available without interrupting the primary task. The user decides what to engage with and when.
Think of the floating "Find & Replace" panel in a text editor — you can type a search term, then click back in your document, edit something, and return to the panel without it disappearing. The tool works alongside you, not over you.
Or the toolbar in a graphic design application, always within reach. Or a progress indicator quietly running in the corner while you continue working. These are modeless patterns — persistent, non-blocking, respectful of your flow.
- Non-Blocking Interaction The main application remains fully interactive while secondary panels, toolbars, or overlays are present.
- Flow Preservation Users can switch between primary and secondary tasks as they choose, without forced checkpoints.
- Complex State Management The system manages multiple simultaneous states — more complex to build, but more powerful in use.
- Productivity Enhancement Expert users move faster when tools are persistent. No reopening, no re-navigating, no lost context.
The Challenge Modeless interfaces can overwhelm new users. With too many simultaneous panels and options, cognitive load rises sharply. The art is in designing modeless experiences that feel open and powerful — not chaotic and confusing. Progressive disclosure is your friend. Try it: Click colors · Drag panels
Design Workspace — Panels Active Main Canvas — Still Active Purple — active fill Colors click to apply Layers ▣ Frame 1 ◻ Button ◻ Text Props W: 340px H: 240px R: 8px Accessibility in Modeless Modeless panels need careful aria-live regions and logical tab order. Screen reader users need to discover and navigate panels without relying on visual position. Draggable panels require keyboard-accessible equivalents. The complexity is real — but essential. Chapter 04 — The Choice
### Neither. Always.
Both patterns are valid. The craft is in knowing which serves the user.
Modal
#### Guided & Focused
- A critical action requires confirmation before it's irreversible
- The user must provide specific input before work can continue
- Security or authentication is required to access a feature
- An error or alert needs immediate acknowledgment
- A sequential workflow demands completion in order
The Risk Overuse causes alert fatigue. Users begin dismissing modals without reading them — defeating their entire purpose. or Modeless
#### Free & Fluid
- Tools or reference information should remain accessible during primary work
- Expert users need efficiency — reopening dialogs wastes time
- Multiple parallel tasks benefit from simultaneous visibility
- Background processes should run without blocking the foreground
- Users have diverse, non-linear workflows that resist forced sequences
The Risk Too much freedom overwhelms new users. Without clear visual hierarchy, modeless interfaces become chaotic. Chapter 05 — Design Philosophy
### The real question is never "modal or modeless?"
The real question is: what does this user need, in this moment, to feel empowered rather than controlled?
01
#### Empathy Before Architecture
Before choosing modal or modeless, ask: who is this person? What are they trying to do? What would frustrate them? What would delight them? Empathy is the first design decision — all others follow from it.
02
#### Cognitive Load is Real
Every modal interrupts working memory. Every modeless panel competes for attention. Both patterns impose cognitive costs. Good design minimizes unnecessary cost while preserving the cost that genuinely serves the user.
03
#### Autonomy as Design Value
Users who feel in control perform better and feel better. Excessive modality signals distrust — as if the system doesn't believe the user can make good decisions. Design that respects autonomy builds trust.
04
#### Context is Everything
A modal for deleting a file: appropriate. A modal to ask about a newsletter: manipulative. A modeless search panel: powerful. A modeless onboarding guide for a complex app: overwhelming. The pattern doesn't determine value — context does.
05
#### Iterate with Real Feedback
No design is right the first time. The best modal-vs-modeless decisions come from watching actual users interact with actual interfaces — not from assumptions, even well-informed ones. Build, observe, learn, adjust.
06
#### Consistency Reduces Friction
When your product uses modals consistently for critical confirmations and modeless panels consistently for tools, users build mental models quickly. Inconsistency is the silent killer of usability — and of trust.
Chapter 06 — The Real Stakes
### Accessible Design is Good Design.
Not a compliance checkbox. Not a nice-to-have feature. The standard by which every design decision is measured.
Here's the truth that elevates modal and modeless from abstract vocabulary to meaningful practice: the choices you make about interface patterns directly determine who can and cannot use what you build.
A modal dialog that doesn't trap focus leaves keyboard users lost in a sea of inaccessible background elements. A modeless panel that relies on drag-and-drop without keyboard equivalents excludes users with motor impairments entirely.
Accessible design is not a checklist you add at the end. It is a lens through which every decision — including modal vs. modeless — is made from the beginning. When you design accessibly, you design better for everyone.
Screen readers, keyboard navigation, motor assist devices, cognitive accommodations, low vision settings — these aren't edge cases. They are the full spectrum of human experience. And your design either includes that spectrum or excludes it. There is no neutral ground.
This is why we say it plainly: accessible design is good design. Not a compliance requirement. Not a nice-to-have. The standard. Everything else is an unfinished product.
01
##### Focus Management in Modals
When a modal opens, focus must move into it. When it closes, focus must return to the trigger. Without this, keyboard users are stranded. Always use aria-modal="true" and trap focus inside the dialog.
02
##### Keyboard Equivalents for Modeless
Any modeless panel or toolbar must be fully keyboard-navigable. Draggable panels need keyboard-accessible positioning. Every visual affordance needs a non-mouse path.
03
##### Live Regions for Dynamic Updates
Modeless interfaces that update dynamically must use aria-live regions so screen readers announce changes. Silent updates are invisible to non-sighted users.
04
##### Cognitive Accessibility
Complex modeless layouts increase cognitive load — especially for users with attention or processing differences. Offer simplified views. Allow users to reduce complexity. Respect their mental bandwidth.
Chapter 07 — Your Playbook
### Practical Design Guidelines
Design guidelines for modal and modeless interface patterns
Situation | Pattern | Why
Confirming a destructive action (delete, reset) | Modal | Forces the user to consciously confirm. Prevents accidental data loss.
Collecting authentication credentials | Modal | Security requires exclusive focus. Nothing else should be accessible until auth is resolved.
Showing a critical error or system alert | Modal | The user must acknowledge the error before the application state is undefined.
Tool palette in a creative or editing app | Modeless | Tools should stay accessible while the user works. Reopening a modal for each tool kills productivity.
Find & Replace in a document editor | Modeless | Users need to search and edit simultaneously. A modal would break the flow entirely.
File download or background task progress | Modeless | Background tasks should never block foreground work. Progress indicators are non-blocking by nature.
Promotional messages or marketing pop-ups | Neither | These interrupt users for the system's benefit, not the user's. This is the modal anti-pattern.
Onboarding a new user to a complex interface | Contextual | Consider a guided modal sequence for first-use, with an option to return via modeless help panels later.
You're ready to design better
### Go build something everyone can use.
Modal and modeless aren't just technical vocabulary. They're a philosophy — about when to lead and when to follow, when to focus and when to free. Master this and you master one of the fundamental rhythms of human-centered design. And when you build accessibly fro

[truncated — full text at https://endash.us/toolkit/items/modal-vs-modeless-exploration-scroll]

---

# Relationship System Intelligence

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/relationship-system-intelligence-scroll
- **Tags**: teamwork, culture, workforce, management, conflict, collaboration, growth, scaling, leadership, alignment, goals, health

Skip to main content
- The Stack
- Third Entity
- Nested Systems
- Principles
- Voices
- Roles
- Patterns
A Reference Scroll on Teams, Leadership, and Coaching
## Relationship Systems Intelligence
Most team problems are not people problems. They are system signals. RSI is learning to see the team as real, treat tension as data, and help the room reveal what it already knows.
Leadership Teams Cross-Functional Work Founders & Executives Coaches & Facilitators RSI SQ EQ 01 01 — The Stack
### Three intelligences. One complete picture.
RSI builds on two prior frameworks — Emotional Intelligence and Social Intelligence — extending them into a third domain that neither alone addresses: the intelligence of the system itself. Click each ring or panel to explore the layers.
Layer 1 Emotional Intelligence (EQ) Understanding and managing your own internal emotional state. The inward-facing layer: self-awareness, self-regulation, and the ability to recognize how your emotions shape your perception of everything around you. Layer 2 Social Intelligence (SQ) Reading and responding to other people’s emotional experience. The outward-facing layer: empathy, attunement, and the skill of connecting meaningfully with individuals one-to-one. Layer 3 Relationship Systems Intelligence (RSI) Seeing the group, team, or organization as an entity in its own right — with its own identity, needs, and intelligence. RSI shifts focus from individuals and their relationships to the system between them. “The system is not merely a collection of individuals. It is a living organism that holds its own intelligence — separate from, and greater than, any single member within it.”
02 02 — The Third Entity
### When people gather, the system arrives too.
Two people create a field. A leadership team creates one too. RSI calls that field the Third Entity. When tension stays fused to people, it sits between them. When you externalize it, they can stand side by side and work it.
Drag the people and switch the lens below
Relationship creates an entity Conflict can be externalized The team is not just individuals in a room. The relationship itself is real and workable.
1 Between us 2 Named out loud 3 Faced together Teams miss it when
- Everyone reports to power, nobody works the team
- Private alliances replace shared leadership
- Conflict gets personalized
- Unspoken rules run the room
- The energy shifts but no one names it
RSI helps them see
- The team has its own identity
- Tension is data, not failure
- The issue can be externalized
- System loyalties are already active
- Something is always trying to emerge
The Third Entity is not owned by anyone. Don’t control it. Help the room see it.
03 03 — Nested Systems
### Leaders live inside more than one system.
Leaders live in multiple systems at once. Function. Leadership team. Exec team. Organization. Most confusion is not competence. It is mixed system loyalty.
Local view Person What am I protecting right now? First container Functional team What is my department trying to defend? Shared leadership Leadership team Are we a team, or a set of alliances? Wider system Executive team or organization What does the wider system need now? Systems within systems Executive system Leadership team Function team Person Leadership example A VP can be loyal to their function and still fail the exec team. If everyone speaks for their silo, no executive identity forms.
RSI move Name the system you are representing right now. Then choose on purpose, not by habit.
Primary system question Which system is primary right now?
04 04 — The Five Principles
### Observable patterns. True across systems.
Not tips. Patterns. If you can see them, you can work with them.
Impose a solution The leader diagnoses the team from the outside, prescribes a fix, and treats tension as a deviation to eliminate. The system may comply for a while, but it has not actually been seen.
Reveal the system The coach or leader names what is happening in the room, externalizes what is stuck, and helps the team discover its own intelligence. The shift comes from better seeing, not better controlling.
01 Each system has its own identity Principle 1 ⌄ A team is not a sum of individuals. It is its own entity. Leaders and new hires join a live system that already has identity, loyalties, and habits.
That is why leadership teams often look like founder one-on-ones instead of a real team. RSI starts by helping the room see the team as real.
Pattern to notice If everyone talks to authority and not to each other, the team identity is still offline.
02 Every member is a Voice of the System Principle 2 ⌄ Every person in a system carries information that belongs to the system — not just to themselves. This includes the quietest person in the room, the contrarian, the cynic, the person who seems to be “the problem.” All of them are expressing something the system is generating.
Deep Democracy is the principle that every voice holds a piece of the truth, and suppressing any voice means the system operates with incomplete intelligence. It isn’t about giving everyone equal airtime — it’s about ensuring every signal is received.
Pattern to notice The loudest objector isn’t necessarily wrong — they may be carrying a signal the system needs to hear. The silent team member may be holding unexpressed data about what isn’t working.
03 The system is naturally intelligent and creative Principle 3 ⌄ Systems are often wiser than they look. What we call dysfunction is frequently intelligence that has not been named yet.
The RSI move is not to impose answers. It is to reveal the system to itself so the team becomes active in its own development.
Pattern to notice Repeated conflict = unanswered system question.
04 Roles organize the system’s behavior Principle 4 ⌄ Systems assign roles — sometimes formally (manager, lead, contributor) and sometimes informally (the peacekeeper, the skeptic, the visionary, the voice of caution). These roles are carried by individuals, but they belong to the system.
Change the person in the role and the new person will often begin exhibiting similar behaviors — because the role, not the individual, is what the system needs. The role persists across different holders.
Pattern to notice When a “difficult” employee leaves and another gradually becomes difficult, the system may be generating that role. The question isn’t who fills it — it’s why the system needs it.
05 Systems are always in emergence Principle 5 ⌄ A relationship system is never static. It is always in motion — moving toward something, even when that something hasn’t been named. What looks like resistance, dysfunction, or chaos is often emergence: the system moving toward its next configuration.
RSI practitioners learn to ask not “what’s wrong?” but “what is trying to happen here?” The momentum of a system is a signal, not an obstacle.
Pattern to notice When change feels impossible to implement, ask what the system is moving toward — not what it’s resisting. Lift the gaze to the larger whole.
05 05 — Voices
### Every voice carries system data. Especially the hard-to-hear ones.
When we filter voices, we lose intelligence. Quiet voices are often carrying the signal the room most needs.
System intelligence accessed Reset Click a voice to amplify it The voice that is hardest to hear is often carrying data the system has not yet learned how to metabolize. RSI listens there not to be nice, but to become more accurate.
06 06 — Roles
### The system assigns the role. The person fills it.
When someone consistently “causes problems,” the instinct is to address the individual. RSI asks a different question: what role has the system assigned them, and why? The same person in a different system often behaves differently — because the role changes. Select a role below.
Select a role above to examine what the system is generating. 07 07 — Pattern Recognition
### Practice the inquiry. Notice what the system is saying.
Read the pattern. Then ask the next better question.
### Start reading the system around you.
RSI isn’t a certification or a training program you complete. It’s a perceptual shift and a practice of helping teams see themselves more clearly. Good systems coaching doesn’t impose answers on a room. It surfaces the intelligence, tension, and possibility already present there.
Get Coaching from Peak Praxis ↗ How does RSI relate to your work? En Dash & Peak Praxis — Relationship Systems Intelligence — &copy; 2026

---

# The OODA Loop

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/the-ooda-loop-scroll
- **Tags**: workforce, communication, stress, focus, agile, outcomes, alignment, planning

Skip to main content
- The Loop
- In the Wild
- Business
- The Algorithm
- History
Decision framework — Boyd, 1976
## The OODA Loop
Four steps. One recursive algorithm. The reason the fastest thinker wins — in a dogfight, a board meeting, or anywhere a decision matters before a window closes.
Explore the loop &rarr; The origin story Observe Orient Decide Act The four phases
### Observe. Orient. Decide. Act.
They’re not equal&semi; one does most of the work. Click any phase below to explore it.
&larr; Click a phase to explore it
The loop runs continuously. No start, no finish, only cycles. The competitive advantage isn’t being smarter at any single phase. It’s completing the whole loop faster than your opponent can respond to your last move.
Phase 01
#### Observe
Raw input from the world. Data, signals, feedback… and the slightly pained expression across the conference table. No filtering yet. Just intake. The quality of everything downstream depends entirely on the honesty of what you allow in here.
Most people think they’re good at this. Most aren’t. We observe selectively, confirming what we already believe and quietly discarding what doesn’t fit.
In practice: A product team reads NPS scores, support tickets, and session recordings before sprint planning. Not what they hoped to hear, but what users actually did. Phase 02 — The schwerpunkt
#### Orient
Boyd called this the schwerpunkt&colon; the main effort, the center of gravity. Observations get filtered through your mental models: culture, experience, analysis, instinct, and bias. All of it at once.
Orient shapes not just what decisions you make, but what you even notice in the first place. A mediocre team with sharp orientation beats a sharp team with poor orientation, every time.
In practice: A founder sees a surge in support tickets not as a bug, but as a latent feature request, because she’s talked to 200 customers and knows the pattern. Phase 03
#### Decide
Select a hypothesis. Choose a path. With strong orientation, this becomes fast, sometimes nearly automatic. With weak orientation, you get decision paralysis wearing the costume of diligence.
In fast-moving situations, the goal isn’t a perfect decision. It’s a good-enough decision before the window closes.
In practice: A sales rep leads with the cost-reduction pitch, not the growth pitch — based on a 30-second read of the room. One second of decide, built on years of orient. Phase 04
#### Act
Execute. But here’s what most frameworks miss: action is not the end. Every action generates new observations, feeding straight back into the loop. You’re not just solving a problem, you’re producing the next data point.
This is why “move fast and learn” isn’t just a startup bumper sticker. It’s mechanically correct.
In practice: Launch to 10% of users. The response data is the next Observe phase. The loop doesn’t pause for reflection… it accelerates. You’re already doing this
### In the wild
OODA isn’t something you adopt. It’s a pattern you already run — automatically, constantly. The question is whether you run it well.
Driving Conversation Sports Markets Observe
Read the road
Brake lights ahead. Wet surface. A merge from the left. A speed sign you weren’t expecting. All processed in under a second.
Orient
Interpret the scene
Experience tells you wet roads extend stopping distance. The merge likely means a slowdown. Threat model updates automatically.
Decide
Choose a response
Ease off the accelerator. Cover the brake. Don’t overcorrect. A micro-decision made faster than conscious thought.
Act
Adjust and loop
Foot lifts. Speed drops. New observations begin immediately. The loop doesn’t pause for acknowledgement.
Observe
Listen + read the room
Words, tone, pace, a slight hesitation before “I think that could work.” All signal, all data.
Orient
Read between the lines
That hesitation signals doubt, not agreement. Your history with this person calibrates the read. Experience is orientation.
Decide
Probe or proceed?
Ask a clarifying question rather than proceeding on false consensus. One decision, correctly made.
Act
Respond
“What’s your hesitation?” Three words. Whatever comes next is the next observation.
Observe
Scan the field
Defender position, teammate movement, ball trajectory, a gap opening on the weak side. All at once.
Orient
Pattern recognition
Ten thousand hours of training converts this into instinct. The elite athlete sees the play before it develops.
Decide
Commit early
Pass to where the teammate will be, not where they are. A bet placed under brutal time pressure.
Act
Execute
Ball released. Result is immediately the next observation. Great players cycle faster than defenses adapt.
Observe
Read the signals
Price action, volume, macro data, a competitor’s press release, customer churn ticking upward.
Orient
Model the context
Experienced investors recognize regime changes before they’re confirmed. Years of loss-tested mental models.
Decide
Size the bet
Position, timing, hedge or hold. Made with incomplete information, by design. Certainty is a lagging indicator.
Act
Execute & observe
The market’s reaction is your next observation. In this loop, acting and observing are nearly simultaneous.
Expertise isn’t knowing more. It’s running the loop faster, with sharper orientation doing the heavy lifting. Applied strategy
### OODA in business
Every strategic advantage you’ve ever admired is, at some level, a loop velocity and orientation quality advantage. Select a scenario to see it play out.
Startup vs. incumbent
The speed asymmetry
Why a 12-person company can outmaneuver a 12,000-person company with superior resources.
Product strategy
The pivot decision
How teams decide—correctly or incorrectly—when it’s time to change course.
Crisis response
When the loop breaks
How organizations freeze during a crisis, and what OODA tells us about exactly why.
The single most common strategic error isn’t a bad decision. It’s an organization stuck between Orient and Decide — running analysis forever while the window closes. Boyd called getting inside an adversary’s decision cycle “collapsing their OODA loop.” In business, that’s what disruption actually is.
On simple systems
### The power of four words
The most powerful systems are often the simplest. Four steps, run recursively, explain an outsized range of human behavior and competitive outcomes. Other fields rediscovered the same loop… Just under different names.
while (alive) { observe (); // gather raw input from the environment orient (); // filter through mental model — the hard part decide (); // select a course of action act (); // execute — generating the next observation } OODA Loop
- Observe
- Orient
- Decide
- Act
PDCA Cycle
- Plan
- Do
- Check
- Act
Scientific method
- Observe
- Hypothesize
- Experiment
- Conclude
Agile sprint
- Plan
- Build
- Review
- Retrospect
Lean startup
- Build
- Measure
- Learn
Design thinking
- Empathize
- Define
- Ideate
- Prototype & test
Observe reality. Form a model. Make a choice. Take action. Start over. No exceptions. Only variations on the loop. Optional deep dive
### The origin story
OODA emerged from a specific, observable puzzle: why did American pilots keep winning air combat despite flying technically inferior aircraft? The answer changed how we think about decisions.
John Boyd — the man behind the loop John Richard Boyd (1927–1997) was a U.S. Air Force fighter pilot, tactician, and strategist who spent most of his career outside official channels and never rose above colonel — partly because he was too disruptive to promote, and too useful to dismiss.
He was known as “Forty-Second Boyd” for a standing bet: starting from aerodynamic disadvantage, he could defeat any pilot in air combat within forty seconds. No one ever collected. He spent the rest of his life trying to understand why he could do this — and turning that understanding into a general theory of conflict.
Korea: the puzzle that started it all In Korea, American F-86 Sabres faced Soviet-built MiG-15s that were technically superior — faster climbers, higher ceiling, tighter turn radius. And yet the F-86 pilots won the engagement ratio decisively.
Boyd’s insight: the F-86 had a hydraulic flight control system and a bubble canopy giving pilots a wider field of view. These features allowed faster situational transitions. By the time a MiG pilot had finished processing one maneuver, the F-86 was already executing the next. Speed of decision, not speed of aircraft.
From a cockpit to everywhere else Boyd spent the rest of his career expanding the framework through a briefing called “Patterns of Conflict” — which he delivered hundreds of times, sometimes for four or five hours. He was not known for brevity. He never published a book. The ideas spread through talks, hand-copied slides, and a devoted circle of people who carried them everywhere.
Boyd died in 1997, largely unrecognized by the institution he served. His ideas outlasted him considerably — which, by all accounts, would have pleased him far more than any promotion.
A Scroll by En Dash Consulting
### Ready to run the loop?
OODA is a lens, not a checklist. Start by asking which phase your team actually gets stuck in — that’s almost always where the leverage is. (Hint: it’s usually Orient.)
Evolve your ways of working &rarr; View Other Scrolls En Dash — Make Work Feel Better Boyd — Patterns of Conflict, 1986

---

# The Pilot Cable

- **Type**: Scroll
- **URL**: https://endash.us/toolkit/items/the-pilot-cable
- **Tags**: focus, agile

An En Dash Scroll
## The Pilot Cable
Before the suspension bridge, before the towers and the deck and the traffic — there was one wire. That wire is the whole idea.
Every bridge starts here
### The gap is not the problem.
In product, in technology, in process — there is always a gap. Two systems that don't talk. A workflow with a break in the middle. A team on one side of a decision, the rest of the organization on the other.
The gap itself isn't the problem. The problem is what most people do next: they imagine the finished bridge and try to build it all at once. They skip the question that actually matters first: can we get anything across at all?
For example
Your CRM and billing system have never spoken
Content lives in Notion, publishing lives in LinkedIn, and the middle is copy-paste
The old approval flow ends at email. The new one starts in Jira. Things get lost between
The first move
### Not a bridge. A proof.
"Don't start with the bridge. Start with the wire."
The pilot cable is the answer. It's the API call that just posts one record. The automation that connects two tools and does exactly one thing. The workflow step that links the old process to the new one — crudely, manually, but actually.
When it lands on the other side, something real has changed. The gap is no longer a gap — it's a connection. Thin, fragile, but real. And from something real, you can build.
For example
One webhook pushing a new order into your CRM — no mapping, just flow
A Zapier action that drafts a LinkedIn post from a Notion title. You still hit publish
A shared spreadsheet bridging the old email approval and the new Jira ticket. Ugly. Working
The evolution
### Each step pulls the next one.
The pilot cable doesn't get replaced — it becomes the foundation. Each stage uses what's already there to pull something heavier across. You can stop at any rung. Not everything needs towers.
01 — Cable The first real connection. It barely carries anything — but it exists. That changes everything.
For example
One API call posting a single record
A manual trigger sending one Slack message
A landing page collecting one email
02 — Rope The connection starts carrying real load. More data, more reliability, more trust. Built entirely on what the cable made possible.
For example
A scheduled two-way sync running hourly
Notion to LinkedIn, triggered automatically on publish
A working prototype used weekly by five real customers
03 — Structure Permanent infrastructure. Trusted, monitored, documented — relied on by people who didn't build it.
For example
A versioned integration with retry logic and alerting
A four-tool workflow documented so anyone can debug it
A paid tier with SLAs and a support queue
04 — Bridge The thing you originally imagined. Arrived at incrementally, built on proof. Every part of it a descendant of that first wire.
For example
A platform integration used across the whole org
A fully automated content engine with analytics and feedback loops
The product you pitched in the first deck — finally real
Where this applies 01 Software & Integration
#### One endpoint. That's the cable.
Don't design the full integration before you've made a single call. Stand up the simplest request that proves the two systems can talk. That's your pilot cable. The sync, the mapping, the error handling — those come later, pulled across by what you just made real.
02 Workflow & Automation
#### Connect first. Automate second.
You don't need the full n8n pipeline on day one. Connect to LinkedIn. Do one thing. That connection is the cable — the thing that makes every subsequent step possible. The scheduling, the Notion sync, the analytics: all of it gets pulled across once the wire is in place.
03 Product & Business
#### Ship the crossing, not the bridge.
The first version of your product isn't the bridge. It's the cable. It creates a real connection between your user's problem and your solution — fragile, minimal, but actual. From there you learn what the rope needs to be. And then the deck. The bridge is what you arrive at, not where you start.
The suspension bridge is the dream. The pilot cable is the work. Start with the wire. Everything else gets pulled across.
En Dash – Make Work Feel Better

---

# Reinvent your Refinement

- **Type**: Workshop
- **URL**: https://endash.us/toolkit/items/reinvent-your-refinement-workshop
- **Tags**: agile, communication, collaboration


### Overview

Refinement sessions are essential for turning vague ideas into actionable tasks, but they can often become routine, ineffective, or overwhelming. By reinventing your approach to refinement, your team can unlock clearer priorities, stronger collaboration, and better-defined outcomes. This workshop equips teams with the tools to transform their refinement processes, ensuring that every session drives progress and alignment.

### Why use this workshop?

This workshop empowers teams to optimize their refinement sessions, making them more structured, focused, and productive. By rethinking how you approach refinement, your team will reduce wasted time, foster a deeper understanding of tasks, and create a more cohesive, results-driven workflow. Through practical exercises, participants will learn to manage the balance between strategic discussions and actionable next steps, enabling more effective planning and execution.

### Who is this for, and when should you use it?

This workshop is ideal for teams that find their refinement sessions lack structure, become drawn-out discussions, or fail to create actionable outcomes. Whether your team is agile, working in sprints, or just looking to improve how they break down work, this workshop will help you streamline your refinement process. It’s perfect for product managers, team leads, and any team seeking to improve clarity and efficiency in their planning sessions.

### How to use this workshop:

1. Use Presentation Mode to introduce the concepts and objectives of reinventing refinement sessions.
1. Align the team on the purpose of refinement and the desired outcomes.
1. Follow guided activities to identify current challenges and implement new strategies for structuring and focusing refinement sessions.
1. Document the new processes and strategies to ensure consistent, long-term improvement.
1. Revisit and refine these processes periodically as your team evolves and new challenges arise.

---

# Streamline your Meeting Cadence

- **Type**: Workshop
- **URL**: https://endash.us/toolkit/items/streamline-your-meeting-cadence-workshop
- **Tags**: teamwork, culture, communication, collaboration


### Overview

Examining existing practices around meetings is crucial for improving productivity and ensuring that team members' time is used efficiently. Meetings are often a significant part of team workflows, but without careful consideration, they can become repetitive, unproductive, or unnecessarily long. By stepping back and assessing how meetings are currently conducted, teams can identify areas where time is wasted, communication is unclear, or decisions are delayed. Establishing a better cadence not only streamlines the process but also ensures that meetings are focused on clear objectives, leading to faster decision-making and more actionable outcomes.
Using this workshop template, teams can expect to collaboratively address the pain points in their meeting structure and work together to create solutions that make meetings more purposeful. Through exercises like the Likert scale and "How Might We..." brainstorming, teams can uncover underlying challenges and generate innovative solutions tailored to their unique needs. By engaging everyone in this process, it fosters a sense of ownership and collective responsibility for making meetings more effective. The benefits of this exercise include more efficient use of time, clearer communication, better engagement, and increased alignment on priorities. The process also helps reduce frustration, ensuring that meetings support the team’s goals rather than becoming a hindrance. Revisiting these practices periodically helps maintain an optimized meeting flow as the team evolves.
This workshop is for any team that is struggling to find common ground within their team. If there is not a smooth workflow or a shared understanding of the way to work, this can inhibit our outcomes and outputs. Your team will build a set of norms that will guide you in the direction of better understanding, collaboration, and culture.

### How to use this workshop

1. Use the workshop in the activities presentation mode
2. Review the introduction materials prior to the start of the workshop for alignment within the team and a shared understanding of the practices that will be discussed
3. Work through the activities as instructed throughout the workshop
4. Document action items and outcomes
5. Revisit this workshop as described for continued results

---

# Team Norms: Async

- **Type**: Workshop
- **URL**: https://endash.us/toolkit/items/team-norms-async-workshop
- **Tags**: async, teamwork, remote, collaboration, communication


### Overview

Setting norms around asynchronous practices is crucial for teams, especially in today’s work environment where remote and flexible schedules are common. Establishing clear async guidelines ensures that communication remains efficient, expectations are managed, and team members are empowered to work autonomously without the pressure of real-time responses. By defining these norms together, teams can reduce misunderstandings, avoid delays, and ensure that everyone is aligned on how and when to communicate and collaborate.

### Why use this workshop?

Using this workshop template helps foster a sense of ownership and inclusion, as all team members contribute to shaping the async practices that best fit their working styles. Additionally, prioritizing and agreeing on these norms ensures that the team is not only productive but also respectful of each other’s time and personal boundaries. By participating in this exercise, teams can expect benefits such as improved collaboration, better focus during deep work, and enhanced work-life balance. The workshop also promotes accountability, as the documentation phase ensures progress is tracked and norms are revisited as the team evolves.

### Who is this for and when should you use it?

This workshop is for any team that is struggling with a packed calendar, overworking because of meetings, unable to focus due to synchronous obligations, or any other scenario similar to this. This workshop will help your team to free up time by implementing asynchronous practices that will allow for a much more enjoyable work environment.

### How to use this workshop

1. Use the workshop in the activities presentation mode
2. Review the introduction materials prior to the start of the workshop for alignment within the team and a shared understanding of the practices that will be discussed
3. Work through the activities as instructed throughout the workshop
4. Document action items and outcomes
5. Revisit this workshop as described for continued results

---

# Modernizing a Regional Insurer’s PMO Portfolio Visibility and Agile and Lean Ways of Working

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=modernizing-a-regional-insurers-pmo-portfolio-visibility-and-agile-and-lean-ways-of-working#what-case-studies
- **Tags**: Ways of Working, Scaling Agile, Tools, Discovery, Jira, Confluence, Atlassian, PMO, OCM, Vendor Management, AI, Operating Model, Roadmap

En Dash assessed a regional insurer’s Jira and Confluence environment, portfolio governance, delivery practices, reporting, capacity visibility, and training needs. The engagement produced a holistic, integrated operating model and phased roadmap for improving consistency, transparency, decision-making, and internal ownership.

---

# Delivering an AI-Assisted Curriculum Implementation Modernization for a Large Urban Public School District

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=delivering-an-ai-assisted-curriculum-implementation-modernization-for-a-large-urban-public-school-district#what-case-studies
- **Tags**: Tools, Education, Ways of Working, AI, OCM

Following a district-wide curriculum realignment to updated state standards, instructors lacked practical implementation guidance for delivering the new curriculum consistently across schools. Existing curriculum documents defined learning objectives but not instructional pacing, sequencing, classroom implementation, or day-to-day teaching guidance. Teachers were required to independently translate standards into lesson plans, creating inconsistent instructional experiences and significant preparation effort.

---

# Developing a International Non-Profit Collective’s Shared Talent Pipeline and Data Governance Model and Roadmap

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=developing-a-international-non-profit-collectives-shared-talent-pipeline-and-data-governance-model-and-roadmap#what-case-studies
- **Tags**: Ways of Working, Discovery, Design, Engineering, Vendor Management, Roadmap

A five-organization nonprofit collaborative needed to connect fragmented talent information and workflows without creating unmanageable technology, privacy, or governance risk. En Dash established a focused minimum viable product, cross-organizational operating model, and phased implementation roadmap.

---

# Executing A Holistic Product Operating Model Transformation for An International Financial Services Organization

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=executing-a-holistic-product-operating-model-transformation-for-an-international-financial-services-organization#what-case-studies
- **Tags**: Ways of Working, Scaling Agile

En Dash provided embedded agile and product coaching, software craft expertise, DevOps guidance, and executive-level consulting across a large international nonprofit’s IT organization. The engagement advanced lean portfolio management, cloud migration planning, delivery automation, product practices, metrics, and leadership visibility while establishing repeatable approaches the organization could sustain and scale.

---

# Building a Scalable Legal Operations and Workflow Model, Leveraging Commercial Solutions, Vibe Coded Apps and Custom Development

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=building-a-scalable-legal-operations-and-workflow-model-leveraging-commercial-solutions-vibe-coded-apps-and-custom-development#what-case-studies
- **Tags**: Legal, Law, Discovery, Vibe Coded Audit, AI, Case Management, Operating Model, Roadmap

En Dash helped a specialized veterans benefits law firm assess fragmented case workflows, define a coordinated future-state operating model, and create a phased roadmap for scalable execution and oversight.

---

# Educating and Enabling A Financial Services Organization’s Move to A Product Operating Model Through Product Design & Discovery Workshops

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=educating-and-enabling-a-financial-services-organizations-move-to-a-product-operating-model-through-product-design--discovery-workshops#what-case-studies
- **Tags**: Design, Discovery

En Dash led product design and discovery workshops to help a financial services organization navigate a major product pivot and move toward a product operating model. Product, design, and software craft consultants aligned stakeholders, rapidly prototyped and validated core experiences, prioritized MVP features, and created a scalable design system for web and mobile. The work prevented misaligned development, accelerated implementation, reduced rework, and gave the internal team a clear product direction it could execute.

---

# Guiding an International Non-Profit’s Agile and Lean Transformation and Cloud Migration

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=guiding-an-international-non-profits-agile-and-lean-transformation-and-cloud-migration#what-case-studies
- **Tags**: Tools, Scaling Agile, Ways of Working

En Dash provided enterprise transformation consulting, embedded agile and product coaching, software craft expertise, DevOps guidance, and lean portfolio management support for a large international nonprofit. The engagement aligned organizational change with cloud migration, delivery automation, portfolio visualization, metrics, and leadership decision-making. The work established repeatable practices, strengthened internal capabilities, and created a scalable foundation for continued agile, lean, and technology modernization.


---

# Providing Comprehensive Product Discovery, Development and Delivery for a Federal Invoice Processing Automation Solution

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=providing-comprehensive-product-discovery-development-and-delivery-for-a-federal-invoice-processing-automation-solution#what-case-studies
- **Tags**: Discovery, Design, Engineering

En Dash led product discovery, product design, architecture, and engineering delivery for a federal invoice-processing platform. The team replaced a fragmented legacy system with an integrated web application using AI, OCR, visual workflow automation, queue management, real-time validation, and unified reporting. The engagement included a complete system-of-record rebuild and historical data migration with zero downtime, preserving agency integrations while reducing manual effort, simplifying training, improving data quality, and creating a scalable foundation for broader automation.

---

# Leading the Development of a Global Service Platform Redesign for an Immigration Services Organization

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=leading-the-development-of-a-global-service-platform-redesign-for-an-immigration-services-organization#what-case-studies
- **Tags**: Discovery, Design

En Dash led product discovery, experience design, technical discovery, and architecture for the redesign of a global immigration services platform. The team created a high-fidelity prototype, modern design system, documented core user flows, and cross-functional review process spanning Product, Marketing, Engineering, and Design. Delivered in eight weeks, the work supported a successful market launch, secured authorization for full development, and established a scalable foundation for continued product delivery.


---

# Modernizing a Leading Financial Services’ Loyalty Platform Documentation Initiative

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=modernizing-a-leading-financial-services-loyalty-platform-documentation-initiative#what-case-studies
- **Tags**: Ways of Working, Developer Enablement, Tools

En Dash led a 16-week documentation modernization initiative for a major financial services loyalty platform spanning 11 business domains. The team assessed existing assets, remediated seven layers of business and technical documentation, implemented modern tooling, and established sustainable governance, maintenance, and knowledge-management practices. The work achieved Enterprise Architecture compliance, streamlined audit response, improved onboarding and developer access to critical information, and positioned the platform as a model for documentation maturity across the enterprise.


---

# Developing a Financial Services Leader’s Interactive Business Capability Map 

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=developing-a-financial-services-leaders-interactive-business-capability-map-#what-case-studies
- **Tags**: Developer Enablement, Ways of Working, Tools, Discovery

Rapid build of interactive, integrated Business-Capability Map to replace alienated powerpoint- and excel-driven workflows

---

# Leading A Retailer’s Product Innovation and Platform Optimization Initiative

- **Type**: Case Study
- **URL**: https://endash.us/what?case-study=leading-a-retailers-product-innovation-and-platform-optimization-initiative#what-case-studies
- **Tags**: Discovery, Design

Product discovery and design to improve critical booking and onboarding workflows

---

# Unstick delivery

- **Type**: Solution
- **URL**: https://endash.us/what?product=hands-on-development-and-delivery#what-products

Work takes longer than it should — and you can feel it.

The drag lives in systems, practices, roles, and decisions. We find it with the people doing the work, then make shipping lighter.

---

# Make AI useful and governable

- **Type**: Solution
- **URL**: https://endash.us/what?product=ai-adoption-and-governance#what-products

AI is moving faster than how you decide and govern.

Pilots stack up. Ownership stays fuzzy. We help you turn experiments into useful, governable practice.

---

# Create shared direction

- **Type**: Solution
- **URL**: https://endash.us/what?product=leadership-alignment#what-products

Leaders and teams aren't pointed the same way.

Priorities compete. Decision rights blur. We align the habits that turn strategy into progress — with you in the room.

---

# See and steer the portfolio

- **Type**: Solution
- **URL**: https://endash.us/what?product=portfolio--governance#what-products

You have portfolio data — but not decisions.

Tools and reports fragment the picture. We build a clearer system for seeing, steering, and learning.

---

# A Thousand Brains: A New Theory of Intelligence

- **Type**: Digest
- **Author**: Jeff Hawkins
- **URL**: https://endash.us/digest/a-thousand-brains-a-new-theory-of-intelligence

A Thousand Brains presents Jeff Hawkins’s theory that intelligence arises from the neocortex building many maplike models of the world through cortical columns, reference frames, prediction, and sensorimotor learning.

---

# An Introduction to the Collected  Works and Wisdom of Tom Gilb: Foundations of Value, Measurement,  and Disciplined Systems Thinking

- **Type**: Digest
- **Author**: John Halberstadt
- **URL**: https://endash.us/digest/an-introduction-to-the-collected-works-and-wisdom-of-tom-gilb-foundations-of-value-measurement-and-disciplined-systems-thinking

A curated, practice-oriented gateway into Tom Gilb’s engineering discipline—value-first thinking, measurable requirements, and evolutionary delivery. Ideal for leaders and practitioners who want rigor, clarity, and evidence-driven improvement in complex systems work.

---

# Building a Storybrand

- **Type**: Digest
- **Author**: Donald Miller
- **URL**: https://endash.us/digest/building-a-storybrand

A practical marketing book that teaches businesses how to clarify their message using a seven-part storytelling framework, positioning the customer as the hero and the brand as the guide.

---

# Deep Work

- **Type**: Digest
- **Author**: Cal Newton
- **URL**: https://endash.us/digest/deep-work

A practical guide to doing high-value, cognitively demanding work in a distracted world. Cal Newport argues that the ability to focus deeply is becoming both more valuable and more rare, and he offers concrete rules for building that skill into everyday professional life.

---

# Drive

- **Type**: Digest
- **Author**: Daniel H. Pink
- **URL**: https://endash.us/digest/drive

The surprising truth about what motivates us.

---

# Linchpin

- **Type**: Digest
- **Author**: Seth Godin
- **URL**: https://endash.us/digest/linchpin

Are you indispensable?

---

# Noise: A Flaw in Human Judgment

- **Type**: Digest
- **Author**: Daniel Kahneman, Olivier Sibony & Cass R. Sunstein
- **URL**: https://endash.us/digest/noise

Why humans make inconsistent judgments and what to do about it.

---

# Nudge

- **Type**: Digest
- **Author**: Richard H. Thaler & Cass R. Sunstein
- **URL**: https://endash.us/digest/nudge

Improving decisions about health, wealth, and happiness.

---

# The Book

- **Type**: Digest
- **Author**: Alan Watts
- **URL**: https://endash.us/digest/the-book

On the Taboo Against Knowing Who You Are

---

# The Culture Code: The Secrets of Highly Successful Groups

- **Type**: Digest
- **Author**: Daniel Coyle
- **URL**: https://endash.us/digest/the-culture-code-the-secrets-of-highly-successful-groups

A practical leadership book about how high-performing groups build strong culture through three learnable skills: creating safety, sharing vulnerability, and establishing purpose.

---

# The Timeless Way of Building

- **Type**: Digest
- **Author**: Christopher Alexander
- **URL**: https://endash.us/digest/the-timeless-way-of-building

A foundational work on architecture, design, and human-centered environments, arguing that living buildings and towns emerge from shared pattern languages, gradual adaptation, and the “quality without a name.”

---

# Thinking, Fast and Slow

- **Type**: Digest
- **Author**: Daniel Kahneman
- **URL**: https://endash.us/digest/tfs

A groundbreaking exploration of the two systems that drive the way we think.

---

# Tiny Experiments

- **Type**: Digest
- **Author**: Anne-Laure Le Cunff
- **URL**: https://endash.us/digest/tiny-experiments

Anne-Laure Le Cunff reframes personal growth away from rigid, linear achievement and toward an experimental approach rooted in curiosity, reflection, and adaptive action. Drawing on neuroscience, philosophy, and practical behavioral tools, the book shows how tiny experiments can help readers navigate uncertainty, make better decisions, and build a more meaningful life on their own terms.

---

# Values-Based Consulting

- **Type**: Digest
- **Author**: John Halberstadt & Caitlin Klink
- **URL**: https://endash.us/digest/vbc

Do good, do better, do well—a guide to ethical, client-centered consulting.

---

# Weapons of Math Destruction

- **Type**: Digest
- **Author**: Cathy O'Neil
- **URL**: https://endash.us/digest/weapons-of-math-destruction

A clear, urgent look at how opaque algorithms shape decisions in education, hiring, policing, credit, insurance, and politics—and how those systems often reinforce inequality instead of fairness.

---

# Zero to One

- **Type**: Digest
- **Author**: Peter Thiel with Blake Masters
- **URL**: https://endash.us/digest/zerotoone

Notes on startups, or how to build the future.

## Events

Workshops, talks, and community gatherings.

- [Ai DevCraft](https://endash.us/events/ai-devcraft) — Las Vegas, 2026-10-26T11:00:00.000-07:00
- [Audit It Yourself: ](https://endash.us/events/audit-it-yourself) — VCU STEM Building - Room 404, 2026-10-16T15:00:00.000-04:00
- [The Product Group: TPG Live Panel September](https://endash.us/events/the-product-group-tpg-live-panel-septem) — 2026-09-11T13:00:00.000-04:00
- [PMI Silicon Valley PMO Leadership Meeting: AI
Governance for PMOs](https://endash.us/events/pmi-silicon-valley-pmo-leadership-meetin) — 2026-08-12T10:30:00.000-04:00
- [Backend Boundaries for Frontend Developers](https://endash.us/events/backend-boundaries-for-frontend-develope) — New York & Online, 2026-09-29T16:15:00.000-04:00
- [Accessibility in the Age of AI: The Robots Are Also Blind](https://endash.us/events/accessibility-in-the-age-of-ai-the-robo) — New York & Online, 2026-09-29T15:00:00.000-04:00
- [PMI 4C - California Central Coast: Agile, Product, and Software Craft in AI-Enabled Delivery](https://endash.us/events/pmi-4c-california-central-coast-agile) — Remote, 2026-09-24T21:30:00.000-04:00
- [PMI California Inland Empire: Practical AI Governance for Delivery Teams: AI Governance for Project Managers: From Principles to Practice in 90 Days](https://endash.us/events/pmi-california-inland-empire-practical) — 2026-08-18T21:00:00.000-04:00
- [Project Management Institute (PMI) Global Summit](https://endash.us/events/project-management-institute-pmi-globa) — Detroit, MI, 2026-10-21
- [PMI Oakland CA Virtual Roundtable: AI Governance for Project Managers: From Principles to Practice in 90 Days](https://endash.us/events/pmi-oakland-ca-virtual-roundtable-ai-go) — Oakland, CA, 2026-07-07T10:15:00.000-04:00
- [Agile Alliance: AI, Agile, and Developer Experience: Designing the New Delivery Loop](https://endash.us/events/agile-alliance-ai-agile-and-developer) — 2026-07-09T11:00:00.000-04:00
- [PMI Los Angeles: Practical AI Governance for Delivery Teams: Helping AI Adoption Succeed Without Losing Control](https://endash.us/events/pmi-los-angeles-practical-ai-governance) — 2026-07-16T21:00:00.000-04:00
- [BuildItTogether](https://endash.us/events/buildittogether) — Dallas, TX, 2026-10-27
- [PMI West Texas: June Lunch and Learn - Agile Meets Product Meets Software Craft in AI-Enabled Delivery](https://endash.us/events/pmi-west-texas-june-lunch-and-learn-a) — 2026-06-09T12:30:00.000-04:00
- [PMI NNV: June Lunch and Learn - Agile Meets Product Meets Software Craft in AI-Enabled Delivery](https://endash.us/events/pmi-nnv-june-lunch-and-learn-agile-me) — National Harbor, MD, 2026-06-23T15:00:00.000-04:00
- [TuxCare Stream](https://endash.us/events/tuxcare-stream) — 2026-06-03T23:00:00.000-04:00
- [n-dx Hackathon Kickoff](https://endash.us/events/n-dx-hackathon-kickoff) — 2026-06-08T17:30:00.000-04:00
- [Bay Area Agile Leadership Network: Agile Meets Product Meets Software Craft in AI-Enabled Delivery](https://endash.us/events/bay-area-agile-leadership-network-agile) — Remote, 2026-05-19
- [Santa Barbara Agile: Agile Meets Product Meets Software Craft in AI-Enabled Delivery](https://endash.us/events/santa-barbara-agile-agile-meets-product) — Remote, 2026-05-28
- [Agile Brigade Canada: ](https://endash.us/events/agile-brigade-canada) — Remote, 2026-08-26T18:00:00.000-04:00
- [DC Lean + Agile Meetup](https://endash.us/events/dc-lean-agile-meetup) — 2026-04-08
- [March Lunch and Learn - Branding Your PM Career: Change Your Narrative — Power Your Next Pivot!](https://endash.us/events/march-lunch-and-learn-branding-your-pm) — 2026-03-25
- [QCon AI Boston 2026](https://endash.us/events/qcon-ai-boston-2026) — Boston University George Sherman Union, Boston, MA, 2026-06-01
- [QCon San Francisco 2026](https://endash.us/events/qcon-san-francisco-2026) — San Francisco, CA, 2026-11-02
- [January Consultants’ Circle](https://endash.us/events/january-consultants-circle) — Remote, 2026-01-20T12:00:00.000-05:00
- [Making Auditing and Assessment Work presented by Tom Gilb](https://endash.us/events/making-auditing-and-assessment-work-pres) — Remote, 2026-01-14T12:00:00.000-05:00
- [AI Governance: 90-Day Plan](https://endash.us/events/ai-governance-90-day-plan) — Remote, 2026-01-14T12:00:00.000-05:00
- [PMI Northern Nevada - Highlights from the PMI Global Summit and Leadership Institute ](https://endash.us/events/pmi-northern-nevada-highlights-from-th) — Remote, 2025-12-18
- [PMI Northern Nevada - Holiday Party at Aces Field](https://endash.us/events/pmi-northern-nevada-holiday-party-at-a) — Aces’ Field, Reno, NV, 2025-12-05
- [Sleigh in Notion, pt 5: Rollups the Red-Nosed Reindeer](https://endash.us/events/sleigh-in-notion-pt-5-rollups-the-red) — Remote, 2025-12-18T12:00:00.000-05:00
- [Sleigh in Notion, pt 4: Run Relations Run](https://endash.us/events/sleigh-in-notion-pt-4-run-relations-ru) — Remote, 2025-12-12T12:30:00.000-05:00
- [Sleigh in Notion, pt 3: Database the Halls](https://endash.us/events/sleigh-in-notion-pt-3-database-the-hal) — Remote, 2025-12-11T12:00:00.000-05:00
- [Sleigh in Notion, pt 2: O Notion Tree](https://endash.us/events/sleigh-in-notion-pt-2-o-notion-tree) — Remote, 2025-12-09T12:00:00.000-05:00
- [Sleigh in Notion, pt 1: North Pole HQ](https://endash.us/events/sleigh-in-notion-pt-1-north-pole-hq) — Remote, 2025-12-04
- [Frontrunners 2026 JS/Web or Data/AI](https://endash.us/events/frontrunners-2026-jsweb-or-dataai) — 2026-03-27
- [Data + AI Summit RVA](https://endash.us/events/data-ai-summit-rva) — Richmond, VA, 2026-03-26
- [CyberconVA 2026](https://endash.us/events/cyberconva-2026) — Richmond, VA, 2026-02-06
- [En Dash Consultants Circle](https://endash.us/events/en-dash-consultants-circle) — Remote, 2025-12-16
- [Project Management Institute (PMI) Annual Global Conference](https://endash.us/events/project-management-institute-pmi-annua) — Phoenix, AZ, 2025-11-12
- [Project Management Institute (PMI) Leadership Institute Meeting (LIM) conference (Chapter Leaders only)](https://endash.us/events/project-management-institute-pmi-leade) — Phoenix, AZ, 2025-11-10
- [En Dash October’s Launch and Learn: Getting Started with AI for Small Businesses](https://endash.us/events/en-dash-octobers-launch-and-learn-gett) — Remote, 2025-10-28
- [Datatune](https://endash.us/events/datatune) — Nashville, TN, 2026-03-06
- [Project Management Institute (PMI) Northern Nevada November Meetup: speaker Caitlin Klink](https://endash.us/events/project-management-institute-pmi-north) — Reno, NV, 2025-11-25
- [Agile Meets Architecture](https://endash.us/events/agile-meets-architecture) — Berlin, DE, 2026-03-10
- [Analysis Everywhere](https://endash.us/events/analysis-everywhere) — Columbus, OH, 2026-03-06
- [analytics and data summit 2026](https://endash.us/events/analytics-and-data-summit-2026) — Redwood Shores, CA, 2026-04-14
- [Agile Alliance Agile 2026](https://endash.us/events/agile-alliance-agile-2026) — National Harbor, MD, 2026-07-26
- [Women in Tech](https://endash.us/events/women-in-tech) — Richmond, VA, 2025-10-30
- [Project Management Institute (PMI) Northern Nevada October Meetup: GenAI-enabled career management for Project Managers](https://endash.us/events/project-management-institute-pmi-north) — Reno, NV, 2025-10-28
- [PMI Northern Nevada Lunch and Learn - GenAI for PMs](https://endash.us/events/pmi-northern-nevada-lunch-and-learn-ge) — 2025-08-28
- [PMI Northern Nevada Professional Development Day](https://endash.us/events/pmi-northern-nevada-professional-develop) — Reno, NV, 2026-04-17