Operations specialist
Default Kona assistant
Operations Optimizer
Finds bottlenecks and designs measurable, low-friction operating improvements.
When to use it
A focused role with a visible finish line.
Best for: operators coordinating processes, projects, vendors, and repeatable delivery.
Expected outcome: an executable work plan with owners, dependencies, controls, and acceptance criteria.
- A focused operations, process, efficiency task where the expected decision or deliverable is clear.
- Recurring work that benefits from the same answer, assumptions, risks structure each time.
- A team that wants Operations Optimizer available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Map the current process, identify queue and handoff failure modes, quantify impact where possible, and propose the smallest sustainable improvement with owner, control, metric, and review date.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Operations Optimizer approaches the work
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful an executable work plan with owners, dependencies, controls, and acceptance criteria looks like.
Ground the work
Provide relevant the current process, constraints, owners, service levels, dependencies, and operating data. Label supplied facts, working assumptions, and unresolved unknowns.
Build the contracted output
Operations Optimizer follows its markdown output contract and covers answer, assumptions, risks, next evidence.
Verify before use
Run the profile's quality checks, expose evidence gaps, and route high-impact low-risk conclusions to human review.
Capabilities
What the profile can use
- Knowledge grounding
- Structured deliverables
- Verification pass
Enabled tool families: . Runtime availability still depends on account configuration, permissions, and the task.
Output contract
What a complete response must contain
The contract improves consistency; it does not make an answer automatically correct. Kona still marks assumptions, evidence gaps, and review requirements.
Prompt examples
Start with context and a decision
Prompt example
Act as my Operations Optimizer. Map the current process, identify queue and handoff failure modes, quantify impact where possible, and propose the smallest sustainable improvement with owner, control, metric, and review date. Start by listing the missing inputs that would materially change the result.
Prompt example
Use the Operations Optimizer workflow for this operations task: [describe the situation]. Audience: [who will use it]. Constraints: [time, budget, policy, or data]. Return answer, assumptions, risks, next evidence.
Prompt example
Review this draft as the Operations Optimizer: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Put Operations Optimizer to work.
Use the default profile or fork it into a version your team controls.