Your small imprecise ask is a big waste of their time
Vague, off‑hand requests from managers and executives can quietly balloon into hours or days of unplanned work, especially when subordinates feel unable to push back or ask clarifying questions. Commenters describe how power distance, skipped hierarchies, and a lack of context or clear priorities lead to burnout, bad code, and wasted effort—yet overly detailed, “micromanaged” asks create their own problems. Many argue the real fix is cultural: normalize clarification, share the “why” behind requests, time‑box exploratory work with psychological safety, and use lightweight written tracking so that priorities and expectations are explicit.
Imprecise asks & scope
- Many comments agree vague requests from leaders cause wasted effort, rework, and stress.
- Lack of context (“why is this needed?”) is as harmful as lack of detail; people often solve the wrong problem (classic “XY problem”).
- Several note that any “offhand” request implicitly reorders priorities; leaders often underestimate this.
- Good practice suggested: ask what’s actually needed vs. what’s being asked, clarify expected output quality, and confirm how it affects other work.
Hierarchy, juniors, and power distance
- Repeated concern about senior leaders bypassing technical leadership to talk directly to juniors.
- Juniors often lack system context and negotiating power; they say “yes” to unrealistic asks and timelines, creating burnout and bad code.
- Others note “telephone game” effects when everything is routed strictly through layers; suggested compromise is involving both ICs and their managers and building psychological safety to push back.
Timeboxing, estimates, and research
- Mixed views on timeboxing (“spend 20 minutes and report back”).
- Pro: lets teams explore unknowns cheaply, improves cost/benefit decisions, surfaces when something is a rabbit hole.
- Con: time is a poor proxy for scope; people feel pressured to optimize for appearances, or they quietly exceed the limit.
- Many emphasize that timebox results must be safe-to-fail and treated as information, not commitments.
Backlogs, tickets, and written requests
- Some advocate closing or backlogging old tickets aggressively; others call that destructive because tickets are documentation and can regain priority.
- Strong support for routing “every” request through a ticket system to track priorities and protect engineers from ad‑hoc interruptions.
- Asking for requests in writing is framed both as healthy (memory, clarity, audit trail) and, in some orgs, as a sign that trust is already broken.
Communication styles & relationships
- Several analogies from personal relationships: literal vs. inferential communication, over- or under-specifying requests, and frustration when initiative misfires.
- Consensus that “leave as little to assumption as reasonable,” but also that overly verbose specs aren’t read. Finding the “right level” is hard and person-dependent.
Culture, good faith, and coping
- Many argue the root issue is culture: fear of questioning, high power distance, and blame games.
- “Good faith” is urged on both sides: leaders thinking before asking; reports avoiding “human command line” or malicious compliance.
- Coping tactics: timebox discovery, clarify priorities explicitly, batch questions, push some costs back to requesters, and, if culture remains toxic, consider leaving.