The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need to send the project capacity plan to Hannah in delivery and to Raj, the resource director,…
Execute — do the immediate task
+I need to send the project capacity plan to Hannah in delivery and to Raj, the resource director, for approval, signers in that order, with a Monday deadline. Before routing, ensure actuals through last month roll into the capacity sheet, confirm the critical-path tasks are flagged, and that contingency headcount is visible by team.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I send the capacity plan to delivery leadership, make it easy to approve: put the resource…
Improve — make it easier to accept
+Before I send the capacity plan to delivery leadership, make it easy to approve: put the resource shortfall per quarter at the top, make staffing assumptions and hire lead times findable, and flag any tasks without owners that would make Hannah hesitate to green-light the schedule.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+Project managers insist hiring will fill gaps; HR says hires take four months. I used current ramp…
Decide — diagnose the stuck moment
+The model shows a two-month resource shortfall starting in September.
Project managers insist hiring will fill gaps; HR says hires take four months. I used current ramp assumptions and now see a two-month shortfall that would delay launch. I cannot tell whether to compress scope, reassign internal bench, or push timeline. What is the probable best move and how should I present trade-offs to Hannah and Raj in one slide?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the past year our capacity plans are repeatedly rebaselined when hires are delayed and task…
Become — change the pattern
+We keep slipping because hiring assumptions and task ownership are vague until late in the quarter.
Over the past year our capacity plans are repeatedly rebaselined when hires are delayed and task owners change, costing credibility. Where is the pattern that wastes our time and what single habit—how we set hiring lead times or lock task ownership—should I change to stop quarterly surprises?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Where the evidence lives
Who was seen doing this, and what people really ask.
Acoustic ConsultantAdaptive Optics EngineerProcess EngineerSpacecraft Operations EngineerFacade DesignerHorticulturistalso: Manage projects and resources
Software tasks in the LLOS Work Atlas come from evidence, never a feature list: careers attested to do the work, real job descriptions, and the questions people actually ask (with their view counts). Facets — feature, workflow, troubleshoot, administer, deploy, scale — are open metadata: the work decides, not a taxonomy.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.