Perform business analysis

Perform business analysis — real work, not an imagined feature: named inside 7 evidenced career tasks. Below are four ready AI prompts for it, one per height of help: do it, make it easier to accept, decide when you are stuck, and change the pattern for good.

7career tasks name it
4prompt heights

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 have to send the business analysis pack for Q2 to the planning committee and to Greg in…
I have to send the business analysis pack for Q2 to the planning committee and to Greg in operations for feedback by Thursday. Confirm the revenue reconciles to the ledger, the headcount changes are explained, the key assumptions are listed, and that the executive summary contains the top three risks and recommended next steps before I circulate.

Improve — make it easier to accept

+
Before I hand this analysis to the execs, make it easy to act on: put the projected cash impact of…
Before I hand this analysis to the execs, make it easy to act on: put the projected cash impact of each recommendation at the top, make the sensitivity of the headline metric findable in one table, flag any data sourced from provisional reports, and call out where additional modelling would change the recommendation.

Decide — diagnose the stuck moment

+
The CEO wants a go/no-go on the pilot based on a single ROI number, but marketing won't provide…

leadership asked for a one-metric decision with incomplete inputs.

The CEO wants a go/no-go on the pilot based on a single ROI number, but marketing won't provide conversion rates and IT can't confirm deployment costs. I'm worried the ROI will be meaningless. What's the likely way leadership will interpret a partial number, what is the best immediate fallback metric to provide, and how should I present the caveats so Greg doesn't get blamed for an optimistic recommendation?

Become — change the pattern

+
We keep doing ad-hoc deep dives into the same demand and cost assumptions every quarter, which eats…

repeated last-minute deep dives from leadership into the same assumptions

We keep doing ad-hoc deep dives into the same demand and cost assumptions every quarter, which eats analyst time and frustrates operations. Where are we losing credibility and efficiency, and which two durable changes to our modelling cadence or ownership of assumptions will stop these recurring crises?

Where the evidence lives

Who was seen doing this, and what people really ask.

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.