Skip to main content

How Can I Desig Workflows That Prevent “Pencil Whipping”?

Learn how to design workflows that encourage thoughtful participation and produce higher-quality data.

Written by Lauren Baird
Updated over a week ago

Answer

“Pencil whipping” occurs when users complete workflows quickly without meaningful observation or engagement. This is often a workflow design issue, not just a user behavior issue. Poorly designed workflows reduce data quality and undermine program credibility.

Workflow Managers can reduce pencil whipping by designing workflows that are clear, purposeful, and evidence-driven.


Steps

  1. Review the workflow from a frontline user’s perspective.

  2. Identify questions that feel repetitive, unclear, or unnecessary.

  3. Replace generic yes/no questions with:

    • Specific prompts

    • Conditional follow-up questions

    • Evidence-based inputs (photos or short text where appropriate)

  4. Break long workflows into logical sections or categories.

  5. Add routing that triggers follow-up questions when risk is identified.

  6. Remove required fields that do not improve insight.

  7. Test the workflow in Demonstration (UAT) and observe completion behavior.

If a workflow can be completed without observing anything meaningful, revise the design.


What Causes Pencil Whipping

Users are more likely to rush when workflows:

  • Feel too long or repetitive

  • Ask unclear or overly generic questions

  • Do not explain why detail matters

  • Allow users to skip meaningful observation without consequence

Good design reduces these risks.


Design Choices That Improve Quality

Encourage thoughtful completion by:

  • Asking clear, specific questions

  • Requiring photos or short text where observation matters

  • Breaking long workflows into logical steps

  • Using conditional routing to trigger follow-up questions

  • Making it easier to do the right thing than to rush


What to Avoid

Avoid workflows that:

  • Overuse required fields without purpose

  • Rely only on yes/no questions for complex topics

  • Force long narrative responses unnecessarily

  • Add friction without improving insight

More enforcement does not automatically mean better data.


What Good Looks Like

Well-designed workflows:

  • Take an appropriate amount of time to complete

  • Capture evidence where it matters

  • Feel fair and reasonable to users

  • Produce data you trust

Users should understand why the workflow matters—not just how to complete it.


👉 Quick Design Check
If a workflow can be completed without observing anything meaningful, revisit the design.


Additional Details

Job Role: Workflow Manager | Permission Level: Admin (ANVL Manager) + ANVL TECH (ANVL Workflows) | Special Rights: Workflow Management (Create / Edit / View / Publish - UAT / Publish-ALL / Admin)

Did this answer your question?