#Outcomes, not steps

Tell Nourva the result you want, and let it find the path there.

#Overview

Nourva works from outcomes, not instructions. You describe the result you want in plain language, and Nourva figures out how to reach it: it understands the goal, plans an approach, carries it out, checks its own work, and reports back with something you can see and reuse. You never have to spell out the individual moves.

This is the core of how Nourva works, and it changes how you ask. Instead of breaking a task into a sequence of commands, you state the destination and trust Nourva to navigate. The result is less effort from you, fewer brittle instructions to maintain, and a clearer separation between what you care about (the outcome) and the mechanics of getting there (Nourva's job).

#Why this works

When you specify steps, you carry the burden of knowing the exact path — and any change along the way breaks your instructions. When you specify the outcome, Nourva adapts as conditions change, choosing the right approach for the goal in front of it. The experience is the same whatever you ask: you state the outcome, Nourva does the work, the result is checked, and you get something you can see and reuse.

  • You stay at the level you actually care about. You know what "done" looks like; you should not have to know every move to get there.
  • Nourva adapts in real time. If a path doesn't work, Nourva tries another — something a fixed list of steps could never do.
  • The result is checked, not just attempted. Every action is automatically verified before it is reported done, so an outcome-focused request still comes back honestly confirmed.
  • Ambiguity is handled, not ignored. When a goal is unclear or risky, Nourva asks first rather than guessing.

#How to write a good outcome-focused request

  1. Name the result, not the procedure. Say what you want to end up with — a document, a comparison, a working site, an answer — rather than how to assemble it.
  2. Be specific about what "good" means. Include the details that matter to you: the audience, the format, the constraints, the things to include or avoid.
  3. Bring what you already have. Links, files, examples, and requirements help Nourva hit the target on the first pass.
  4. Choose a permission level that fits. Start cautious when you're exploring, and give more freedom for long, well-understood tasks you trust. You can change the level at any time, and stopping always works immediately.
  5. Steer from the result, not the steps. If the outcome isn't quite right, describe what to change about the result in plain language and let Nourva adjust.
Tip

If you find yourself listing steps, pause and ask: what am I actually trying to end up with? State that instead. Nourva is far better at finding a path than at following one you've half-specified.

#Examples

What you ask:

text
Compare the three project-management tools I've been looking at and tell me which fits a small remote team best.

What you see: A comparison laid out side by side against the things that matter for a small remote team, with a clear recommendation — not a transcript of every page that was checked.

What you ask:

text
Build me a simple landing page for a weekend pottery class — friendly, with a signup form.

What you see: A working page you can open and use, matching the tone you described, that you can refine in plain language until it's right.

A weak request and a strong one for the same goal:

Weak (step-focused)Strong (outcome-focused)
"Open the analytics page, copy the numbers, paste them into a sheet, then make a graph.""Show me last quarter's signups as a chart so I can see the trend."
"Search five sites, read each one, and summarize them.""Research the current state of home solar incentives and give me a report with sources I can check."

The strong version names the result and the format; Nourva chooses how to get there and presents it in the way that best fits.

#Tips

  • Lead with the noun, not the verb. "I want a report on…" or "I need a comparison of…" frames the outcome immediately.
  • Say what you don't want, too. Constraints ("keep it under one page," "no jargon," "only sources from this year") sharpen the result as much as requirements do.
  • Let Nourva pick the format, then ask for a different one if needed. Nourva chooses among table, chart, report, comparison, dashboard, media gallery, alert, and source pack automatically — you can always request another.
  • Watch the first run on a new kind of task. Seeing the work happen helps you learn how to phrase the outcome even more clearly next time.