Voice and tone
Voice is consistent. It reflects the character of the product. Tone shifts with context, reflecting the user's emotional state at a given moment. NimbusWiz has one voice and many tones.
The NimbusWiz voice
NimbusWiz is an enterprise product that helps teams make high-stakes decisions about critical infrastructure. The voice reflects that context: it's professional, direct, and confident, without being cold, jargon-heavy, or presumptuous.
Four voice attributes
Direct without being terse: NimbusWiz copy says what it means without unnecessary preamble. It doesn't say "In order to begin the registration process, you will need to go to the Systems section." It says "To register a system, go to Systems."
But directness isn't the same as brevity at the cost of clarity. When context helps the user act, context stays in.
Specific without being technical: NimbusWiz copy names the thing. Not "an error occurred" but "couldn't reach nimbus-alpha-001." Not "action required" but "run a scan to investigate." Specificity isn't jargon, it's precision in plain language.
Technical users (DevOps Engineers) will appreciate the specificity. Non-technical users (Technical Managers) will appreciate that the specificity is in plain language, not API terms.
Human without being casual: The product is enterprise software. The voice doesn't use exclamation marks, emojis, or chatty language. But it also doesn't use passive constructions, impersonal phrasing, or bureaucratic hedging.
"Your systems are looking healthy" is human. "All monitored systems are currently within acceptable operational parameters" isn't.
Confident without being presumptuous: NimbusWiz copy assumes competence. It doesn't over-explain, repeat itself, or add unnecessary reassurance. It also doesn't assume the user has read the documentation or remembers everything about a feature they haven't used recently.
Confidence means giving users enough to act, not so little they're lost, not so much they feel talked down to.
Tone by context
Onboarding
Emotional state: Curious, slightly uncertain, evaluating.
Tone: Warm, encouraging, low-commitment.
The user is deciding whether NimbusWiz is worth their time. Onboarding copy reduces friction and anxiety without being cheerleader-y.
| Avoid | Prefer |
|---|---|
| "Welcome aboard!" | "Let's set up your organization." |
| "You're going to love this!" | "It takes about 2 minutes." |
| "Complete these steps to get started." | "You can change everything later." |
| "Ready to get started?" | "New here? Here's a 3-minute tour." |
Errors and failures
Emotional state: Frustrated, confused, possibly under pressure.
Tone: Calm, specific, action-oriented.
This isn't the moment for personality. The user needs to know what went wrong, why, and what to do next, in that order, as concisely as possible.
| Avoid | Prefer |
|---|---|
| "Oops! Something went wrong." | "Scan failed: couldn't reach [system]." |
| "Please try again later." | "Check your network connection and retry." |
| "Invalid input." | "System ID must follow the format nimbus-[name]-[number]." |
| "An error has occurred." | Name the error. Name the cause. Name the fix. |
Error messages aren't the place for brand personality. They're the place for information.
Success states
Emotional state: Relieved, moving quickly, ready for the next step.
Tone: Brief, affirming, forward-pointing.
Success states should confirm what happened and, if relevant, indicate what comes next. They shouldn't be long.
| Avoid | Prefer |
|---|---|
| "Congratulations! Your deployment was successful!" | "Deployment complete." |
| "Great job! System registered." | "System registered. Run a scan to begin assessment." |
| "You did it!" | [Nothing: or a status indicator, not a celebration] |
Brief affirmation is appropriate. Celebration isn't. The user has work to do.
Tooltips and helper text
Emotional state: Curious, in the middle of a task, wants a quick answer.
Tone: Informative, compact, no throat-clearing.
A tooltip has one job: answer the question the user was about to ask. It shouldn't repeat the label it's attached to. It shouldn't give a dictionary definition. It should give one to two sentences of genuinely useful context.
| Avoid | Prefer |
|---|---|
| "Stability Index: the stability of the system" | "Reliability and uptime consistency, scored 0–100. Below 50 means high risk." |
| "Click here for more information." | Give the information. |
| Tooltips that open documentation | Tooltips that answer the question |
Destructive or irreversible actions
Emotional state: Cautious, wants to be sure.
Tone: Precise, honest about consequences, non-alarmist.
For actions that can't be undone (rollback, key revocation, user removal), the copy should name the specific consequence without catastrophising.
| Avoid | Prefer |
|---|---|
| "Are you sure?" | "Roll back deployment? The system will return to its pre-deployment state." |
| "Warning! This can't be undone!" | "This key will be revoked immediately. Update any integrations using it first." |
| "Delete" (for permanent deletion) | "Remove [user name] from the organization" |
Name what's being done and what can't be recovered. Don't add drama. Don't add excessive friction.
What NimbusWiz doesn't say
| Never use | Use instead |
|---|---|
| Please | [Remove: or rewrite as a direct instruction] |
| Simply | [Remove] |
| Just | [Remove] |
| Easy | [Remove: let the simplicity speak for itself] |
| Powerful | [Remove: describe the specific capability instead] |
| Seamless | [Remove] |
| Leverage | Use |
| Utilize | Use |
| In order to | To |
| At this time | Now |
| Feel free to | [Remove] |
| Don't hesitate to | [Remove] |