Room for initiative
BeforeA useful extra action waits outside the visible work.
With SkillSmithCreate an ad hoc task and access published resources within the person's permissions.
Add, repeat or delegate a task
Add the extra action a particular work case needs
Attach a one-off follow-up to the existing case with a task description, recipient, optional resource and deadline.
Add ad hoc task; Repeat prepared work Delegate permitted task; Attach follow-up
Roles, playbooks and a practical launch plan for your team.
Turn an improvement idea into a concrete next task
Pay only when you see results
Agree the outcome for your first workflow with our team.
Trusted by leading organizations
“SkillSmith has always been very professional and responsive throughout the entire process and an absolute pleasure to work with.”
Paul HildebrandDirector of HSE/DOT, Jones Power
Add, repeat or delegate a task
Which extra action and recipient belong to this existing work case?
Start with task description and recipient. This method makes task instance and responsibility and case context available within its permitted scope.
WORKED DECISION
Attach the action needed outside the sequence
| Decision point | Information to use | Responsible next step |
|---|---|---|
| Inputs to review | Task description and Recipient | Add ad hoc task. |
| Method action | Optional resource, Deadline and Existing case | Repeat prepared work and Delegate permitted task. |
| Result to inspect | Task instance and Responsibility and case context | Inspect the available result within the permitted scope. |
Connected work across your team
Add, repeat or delegate a task
Start with task description and recipient. The steps below show the actions and information available for this method.
Individual for own work; manager for authorized team
Add ad hoc task; Repeat prepared work
Start with task description and recipient. Add ad hoc task and Repeat prepared work.
- Task description
- Recipient
Individual for own work; manager for authorized team
Delegate permitted task; Attach follow-up
Delegate permitted task and Attach follow-up. The result includes task instance and responsibility and case context.
- Task instance
- Responsibility and case context
The difference in your team’s day
Clear ownership and handoffs
BeforeThe next person receives an action without the preceding result.
With SkillSmithKeep the preceding result attached when the next responsible person receives work.
Fewer repeated choices and inputs
BeforeKnown case details are requested again at the next handoff.
With SkillSmithCarry known context forward and show the decisions needed for this task.
Connected information and agent support
The materials that make this method usable
Keep the relevant material available at the point it is used. The resource choices below support different parts of the work.
Your work context
Information to use
Task description, Recipient, Optional resource, Deadline and Existing case.
A result to inspect
Task instance and Responsibility and case context.
We bring the relevant
context into your work
InputsProduct method
Inspect the result
Add, repeat or delegate a task
- The job context
- Your approved instructions
- A clear response
Available to the right team member
Add, repeat or delegate a task
A specific work need arises
Task instance and Responsibility and case context.
Keep the conversation moving
Take the method into your team's discussion
Use the product sheet to review the roles, materials, workflow and setup choices together.
- The full working method and the focused decision
- Responsibilities and useful materials
- A practical starting plan
PDF · 6 pages
Our delivery approach
Set up a useful first example
Start with the materials and people you already have. We help make the setup choices explicit before your team uses the method.
- 01
Choose the working inputs
Review task description, recipient, optional resource, deadline and existing case.
What we prepare togetherThe inputs and scope for this method are clear.
- 02
Agree who will use the method
Confirm the relevant people and their permitted scope: Individual for own work; manager for authorized team.
What we prepare togetherPeople use the method within the agreed responsibility and access.
- 03
Try the useful actions
Add ad hoc task, Repeat prepared work, Delegate permitted task and Attach follow-up.
What we prepare togetherThe next responsible person and requested work are recorded.
Talk with our team
We are here to help
Bring us the work your team wants to improve. We’ll walk through your instructions, responsibilities and review criteria, then show how our platform can support that work.
Bring your work; we help prepare the method
We work with your team to organize the source material, responsibilities and review choices. Start with one useful example, then carry the agreed method into everyday work.
Your materialUse the instructions, forms and references your team already maintains.
Practical preparationConnect the material to the people and responses needed for the method.
A useful walkthroughTry the ordinary route and the point where your team needs a different decision.
Rohit Singh
VP of Strategic Partnerships
Connecting your workflows with the systems and partners you rely on.
Brent Jackson
Director of Customer Success
Helping your team turn procedures into practical learning and task completion.
Your questions
Prepare the method for your team
What can we inspect after using this method?
The method provides task instance and responsibility and case context. The next responsible person and requested work are recorded.
Who uses this method?
The permitted roles are Individual for own work; manager for authorized team. Confirm the people and their access for the selected example.
Which choices do we need to make first?
Review task description, recipient, optional resource, deadline and existing case. Use those choices to prepare the first example and its permitted scope.
Which extra action and recipient belong to this existing work case?
The required action is outside the prepared sequence; add the specific follow-up with its context instead of silently rewriting the reusable method.