<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/context-constraints-and-consequences-4r3bcxcao" -->

---
title: Context, constraints and consequences | daily.dev
description: Managers can get their reports back on strategic priorities by giving context, constraints and consequences, using a dashboard-versus-access-controls scenario...
canonical: https://daily.dev/posts/context-constraints-and-consequences-4r3bcxcao
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Context, constraints and consequences | daily.dev
og:description: Managers can get their reports back on strategic priorities by giving context, constraints and consequences, using a dashboard-versus-access-controls scenario...
og:url: https://daily.dev/posts/context-constraints-and-consequences-4r3bcxcao
og:image: https://api.daily.dev/og/posts/4R3BCxCAo.png
og:image:alt: Context, constraints and consequences
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Context, constraints and consequences

**[Tech Lead Digest](https://daily.dev/sources/techleaddigest)** · 7 min read · 0 upvotes · 0 comments

## Summary

Managers can get their reports back on strategic priorities by giving context, constraints and consequences, using a dashboard-versus-access-controls scenario as the example. Context means explaining why a priority matters, not just stating it. Constraints remove ambiguity by setting a deadline and standard, like shipping an access control preview by Friday and production by the following Friday. When priorities still get ignored, managers should ask curious questions instead of confronting, then escalate through a team call, a 1:1, and finally a performance improvement plan if behavior doesn't change.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://michaelheap.com/context-constraints-consequences>

## Questions this post answers

### How do I get my team to actually work on the priority I set instead of other useful work?

Provide context explaining why the priority matters, not just that it is the priority, set explicit constraints like deadlines and standards to remove ambiguity, and address ignored priorities with curiosity rather than confrontation. If behavior still doesn't change, escalate through a team call, then a 1:1, then a documented performance improvement plan.

_daily.dev surfaces management and leadership writing for engineers stepping into people management._

### What should I say when a report worked on the wrong thing instead of the priority I set?

Lead with curiosity instead of confrontation, asking something like 'what am I missing about the work that led you to focus there' rather than demanding why they didn't follow instructions. This surfaces whether there was a legitimate reason, like an at-risk customer, or whether they simply defaulted to familiar work they knew how to start.

_Managers navigating tough priority conversations can find more leadership guidance on daily.dev._

## Similar posts on daily.dev

- [Blessed With Constraints: Part II](https://daily.dev/posts/blessed-with-constraints-part-ii-g3x58iqd9) · Tech Lead Digest · 0 upvotes · 0 comments
- [Shift happens: Finding and fixing the gap between strategic intent and actual work](https://daily.dev/posts/shift-happens-finding-and-fixing-the-gap-between-strategic-intent-and-actual-work-vbrpshcyr) · Atlassian · 0 upvotes · 0 comments
- [How to Prioritize as a Product Manager – Product Prioritization Frameworks Explained](https://daily.dev/posts/how-to-prioritize-as-a-product-manager-product-prioritization-frameworks-explained-lpm4ynnpv) · freeCodeCamp · 1 upvotes · 0 comments
- [When the Time Is Right](https://daily.dev/posts/when-the-time-is-right-ldzqcdvhj) · Telerik · 0 upvotes · 0 comments
- [The Critical Skill Nobody Teaches You](https://daily.dev/posts/the-critical-skill-nobody-teaches-you-46olbcmam) · Code Like A Girl · 3 upvotes · 0 comments

---

Tags: [#leadership](https://daily.dev/tags/leadership)

[View this post on daily.dev](https://daily.dev/posts/context-constraints-and-consequences-4r3bcxcao)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Context, constraints and consequences","url":"https://daily.dev/posts/context-constraints-and-consequences-4r3bcxcao","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/context-constraints-and-consequences-4r3bcxcao"},"datePublished":"2026-11-19T16:01:54.496Z","dateModified":"2026-11-19T16:02:22.124Z","description":"Managers can get their reports back on strategic priorities by giving context, constraints and consequences, using a dashboard-versus-access-controls scenario...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/081f7f28839ba5fa5f279ca71c4364b5?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/081f7f28839ba5fa5f279ca71c4364b5?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Tech Lead Digest","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Tech Lead Digest","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/6ed1ee1a2e5c49f698265a6b2912b80d","url":"https://daily.dev/sources/techleaddigest"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/context-constraints-and-consequences-4r3bcxcao","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"leadership","timeRequired":"PT7M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Tech Lead Digest","item":"https://daily.dev/sources/techleaddigest"},{"@type":"ListItem","position":3,"name":"Context, constraints and consequences"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/context-constraints-and-consequences-4r3bcxcao#faq","mainEntity":[{"@type":"Question","name":"How do I get my team to actually work on the priority I set instead of other useful work?","acceptedAnswer":{"@type":"Answer","text":"Provide context explaining why the priority matters, not just that it is the priority, set explicit constraints like deadlines and standards to remove ambiguity, and address ignored priorities with curiosity rather than confrontation. If behavior still doesn't change, escalate through a team call, then a 1:1, then a documented performance improvement plan. daily.dev surfaces management and leadership writing for engineers stepping into people management."}},{"@type":"Question","name":"What should I say when a report worked on the wrong thing instead of the priority I set?","acceptedAnswer":{"@type":"Answer","text":"Lead with curiosity instead of confrontation, asking something like 'what am I missing about the work that led you to focus there' rather than demanding why they didn't follow instructions. This surfaces whether there was a legitimate reason, like an at-risk customer, or whether they simply defaulted to familiar work they knew how to start. Managers navigating tough priority conversations can find more leadership guidance on daily.dev."}}]}
```

