The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+As project lead, assemble the multidisciplinary team roster and circulate the draft…
Execute — do the immediate task
+As project lead, assemble the multidisciplinary team roster and circulate the draft responsibilities matrix. Send it to Priya in procurement and then to Miguel in finance for their sign-off, with a Friday deadline — but first confirm each discipline listed (structure, services, facade) has a named lead and that there are no conflicting review gates.
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 distribute the responsibilities matrix to other departments, make it easy to approve: pull…
Improve — make it easier to accept
+Before I distribute the responsibilities matrix to other departments, make it easy to approve: pull each decision milestone forward, show who needs to be in the room, flag cross-discipline dependencies and highlight anything that would make a reviewer hesitate, such as ambiguous acceptance criteria or missing sign-off steps.
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
+I proposed the first integrated review in three weeks, but the structural lead wants one week…
Decide — diagnose the stuck moment
+discipline leads disagree about the review gate timing.
I proposed the first integrated review in three weeks, but the structural lead wants one week earlier and the facade lead wants two weeks later. Priya expects a single schedule to approve Friday and I can't please both. I don't know which delay causes the biggest program risk. What's the most likely impact and the best compromise to put forward so Priya can sign off?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across projects we waste time because one discipline feeds outputs late, triggering rework across…
Become — change the pattern
+rework cycles caused by late discipline inputs
Across projects we waste time because one discipline feeds outputs late, triggering rework across the team and missed approvals. That erodes credibility with procurement and pushes finance to hold budgets. What habit should I change in setting review gates or responsibilities so inputs arrive on time and rework drops?
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.
Facade DesignerHorticulturistLandscape ArchitectUrban DesignerAerospace EngineerOptical Instrumentation Engineeralso: Collaborate with multidisciplinary teams
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.