The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Build the intake form for new vendor requests with the fields Procurement Lead, Vendor Name, Tax…
Execute — do the immediate task
+Build the intake form for new vendor requests with the fields Procurement Lead, Vendor Name, Tax ID, Risk Level (low/medium/high), Requested By, and Submission Date. Make Vendor Name and Tax ID required, add dropdowns where noted, and enable responses to be collected into a table that procurement can export as CSV. Share the form with the procurement team with edit rights.
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 publish the vendor intake form, reduce back-and-forth with requesters. Surface the three…
Improve — make it easier to accept
+Before I publish the vendor intake form, reduce back-and-forth with requesters. Surface the three missing-items that delay approval: complete tax ID, vendor classification, and at least one contract contact. Add inline help text and make those fields required, and highlight any entries missing documents so procurement sees them on the form response row.
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 rolled out the new vendor request form and several users report their uploaded certificates…
Decide — diagnose the stuck moment
+Users say the form isn’t saving their attachments
I rolled out the new vendor request form and several users report their uploaded certificates disappear after submission. I am Dan in Procurement and worried we will miss missing documents during review. I cannot tell whether this is a permissions issue on the storage location or a form field configuration problem. What is most likely wrong and what steps should I take now to capture those files reliably?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Each week procurement spends an hour cleaning form responses: renaming attachments, filling missing…
Become — change the pattern
+Form responses require manual cleaning before review each week
Each week procurement spends an hour cleaning form responses: renaming attachments, filling missing fields, and exporting to CSV. I own the process and want fewer manual steps. Where do we lose time most — in required fields, storage, or naming conventions — and what one rule change should we enforce to make responses review-ready on arrival?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other word processor work people do in Microsoft Word.
Counsel workers about job and career issuesCreate and apply headingsCreate and format captions for figuresCreate and format cover pageCreate and format headers for sectionsCreate and review banquet event orders (BEOs)Create and update indexesCreate and update table of contentsCreate bulleted listsCreate custom styles
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.