Provide recommendations on financial matters

Provide recommendations on financial matters — real work, not an imagined feature: named inside 16 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.

16career 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

+
Prepare recommendations on whether to reallocate $400,000 from the R&D budget to the marketing…
Prepare recommendations on whether to reallocate $400,000 from the R&D budget to the marketing campaign starting next quarter. Send the recommendation memo to Priya the head of product and Ravi the VP of Marketing for approval, include a clear bottom-line recommendation, expected ROI over 12 months, and a sensitivity table. Ask for sign-off by Thursday so procurement can update vendor contracts.

Improve — make it easier to accept

+
Before I present to the executive committee, make the recommendation easy to approve—pull the…
Before I present to the executive committee, make the recommendation easy to approve—pull the one-line expected ROI to the top, show worst/likely/best cases for revenue impact, identify three risks that would make me reverse the reallocation, and flag any contractual or compliance blockers that procurement should review.

Decide — diagnose the stuck moment

+
I drafted a proposal to move $400,000 from R&D to marketing; Ravi, VP of Marketing, verbally pushed…

The VP of Marketing pushed for the reallocation without data.

I drafted a proposal to move $400,000 from R&D to marketing; Ravi, VP of Marketing, verbally pushed this at the last meeting but hasn’t provided performance data. Priya wants numbers. I fear I’ll approve a politically driven shift that hurts long-term product timelines. What is the most likely reality behind Ravi’s push and what minimal tests or numbers should I demand before I recommend approval?

Become — change the pattern

+
Across several cycles we reallocate budget to loud stakeholders and later regret slower product…

We keep reallocating budgets on anecdotes, not metrics.

Across several cycles we reallocate budget to loud stakeholders and later regret slower product delivery. I own the recommendation memos. What recurring habit is costing us time and credibility, and what single change to my process will stop reactive reallocation and force a simple data gate before any budget move?

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.