How to Handle a Mischievous Mouse

In this process, we aim to effectively address the situation of a pesky mouse causing trouble. By following these steps, you can take control and find a solution, whether it involves getting assistance or seeking alternative measures.

Best Practices for Writing

Use clear, action-first language so readers know exactly what to do and when. Keep sentences short, direct, and focused on the task.

• Start steps with a verb.
• Use concise, plain language.
• Keep terminology consistent throughout the document.
• Proofread for clarity, grammar, and consistency before publishing.

Recommended phrasing

• “Select the Settings icon.”
• “Enter the mouse trap location.”
• “Review the results and update the record.”

Not recommended phrasing

• “You will need to be selecting the settings icon at this time.”
• “What you should do next is to maybe enter the mouse trap location.”
• “Check things and then maybe change whatever needs changing.”

Aim for one action per step and avoid extra commentary inside steps.

---

General Formatting and Writing Guidance

Apply consistent formatting rules so users can scan and follow instructions quickly.

• Capitalize only:
  • Proper nouns (names like Thomas, Zeke, Ginger, Rick).
  • Titles/headings.
  • UI labels exactly as they appear on screen.
• Use numbered lists for sequential actions.
• Use bullet lists for unordered information or options.
• Use bold for UI elements users can see (buttons, fields, links).
• Use italics sparingly for emphasis or definitions.
• Avoid underline in body text to prevent confusion with links.

Numbered list example (for procedures)

1. Prepare to catch the mouse.
2. Encourage your partner or pet.
3. Reconsider your strategy.

Bulleted list example (for non-sequential items)

• Roles involved in handling the mouse.
• Tools available.
• Follow-up actions.

Inline formatting examples

• Select the Start button to begin.
• Optional: Add a note about the mouse’s last known location.

---

Screenshot Guidance

Use screenshots only when they clarify something that words alone cannot easily explain.

• Include a screenshot when:
  • The UI is complex or not intuitive.
  • Users need to recognize a specific screen, icon, or control.
• Size screenshots so:
  • Text and key elements are legible.
  • The image provides enough context without showing unnecessary clutter.
• Use borders or callouts only when needed to highlight the exact area users must focus on.
• For accessibility:
  • Treat purely decorative screenshots as decorative.
  • Provide meaningful alt text only if the screenshot conveys essential information not otherwise described in the text.

---

Job Aid Structure

A standard job aid should follow a predictable structure so users know what to expect.

1. What it is (brief description/purpose)
   • Example: “This job aid describes how to handle a mischievous mouse using available help from your partner or pet.”
2. Security roles (initiators/reviewers/approvers)
   • Example: “Initiator: Household member who notices the mouse. Reviewer: Partner. Approver: Pet owner.”
3. How you do it (procedural steps with an opening sentence)
   • Example opening sentence: “To handle a mischievous mouse, review the roles and complete the following steps.”
   • Then list the steps using action-first phrasing.

Sample phrasing:

• “Use this job aid to guide you through the process of addressing a pesky mouse.”
• “Initiators start the process, reviewers confirm actions, and approvers finalize the decision.”
• “To complete this task, follow the steps below in order.”

---

To handle a mischievous mouse, log in and complete the following steps.

1. Prepare for action as you set out to catch the elusive mouse once again.
2. Encourage your partner or pet to focus and attempt to catch the mouse.
3. If the attempts are unsuccessful, reconsider your strategy while waiting for further assistance, such as a food delivery that is expected in 20 minutes.
4. Plan to acquire a more effective solution or service to address the issue, with confidence in its proven track record.
5. Reassure your partner or pet, acknowledging their effort, and recognize that the previous attempts didn't yield the desired results.

---

General Wording/Phrasing Guidelines

Use consistent terminology and clear phrasing across all steps.

• Use “email” (not “e-mail”).
• Capitalize UI elements exactly as they appear (for example, My Tasks).
• Use “My Tasks” instead of “Inbox.”
• Use “Select” instead of “Click.”
• Use direct, neutral language and avoid slang.

Do

• “Select My Tasks to review your work items.”
• “Enter the mouse details in the Description field.”
• “Select Submit to finish.”

Don’t

• “Click on your inbox to see stuff.”
• “Hit the button to do the thing.”
• “Smash the Submit button when you are ready.”

Align phrasing with how users see labels on screen and keep tone professional and straightforward.

---

Routing Guidance

Describe how users typically navigate to tasks so they can choose the most efficient route.

Common routing patterns:

1. Via applications
   • Example: “Select the Home application, then select My Tasks to view assigned actions.”
2. Via search bar
   • Example: “Search for and select ‘Mouse Handling’ to open the task.”
3. Via worker profile or equivalent
   • Example: “Search for and select the worker’s name, then select the Actions tab to view related tasks.”

Prerequisites:

• Ensure the user has appropriate access or role to see the application or task.
• Confirm the task name and application name match what appears in the system.

Sample instructions:

• “Select the Tasks application and locate the mouse-related item.”
• “Search for and select ‘Mouse Incident Report’ from the search results.”
• “From the worker’s profile, select the History tab to review prior mouse encounters.”

---

Navigational Elements

Use consistent phrasing for UI elements so users can easily map instructions to what they see.

• Buttons
  • “Select Submit.”
  • “Select Cancel to discard changes.”
• Icons
  • “Select the Settings icon.”
  • “Select the Search icon to open the search bar.”
• Checkboxes
  • “Select Enable Mouse Alerts.”
  • “Deselect Enable Mouse Alerts if you no longer want notifications.”
• Comments
  • “Enter a comment in the Comments field, as applicable.”
• Attachments
  • “Select Add Attachment to upload a file.”
• Pop-up windows
  • “Review the information in the pop-up window, then select OK.”
  • “Close the pop-up window if it does not apply.”

Example sentences:

• “Select the Save button to keep your changes.”
• “Select the Info icon for more details.”
• “Select/Deselect the Notify Partner checkbox as needed.”
• “Enter notes in the Comments section about the mischievous mouse.”

---

Step Guidance

Label non-required steps clearly so users know what is optional versus conditional.

• Optional
  • Use when the step is nice-to-have but not required to complete the task.
  • Prefix the step with “Optional:”.
• As applicable
  • Use when the step is conditional and only applies in certain scenarios.
  • Prefix the step with “As applicable:”.

Optional examples

• “Optional: Enter additional details about the mouse in the Notes field.”
• “Optional: Attach a photo of the mouse’s last known location.”
• “Optional: Notify your partner via email about the status.”

As applicable examples

• “As applicable: Select Reschedule if the mouse was not caught.”
• “As applicable: Update the Status field to ‘Resolved’ once the mouse is handled.”
• “As applicable: Add a comment explaining why the attempt failed.”