What it is
The practice of a team using its own product for real tasks, so builders experience the product as users do and surface issues early.
When to use it
During Prototype and Implement, continuously, especially for tools the team can plausibly use themselves.
Why (value)
Creates constant, cheap pressure on quality and surfaces friction that only shows up in sustained real use.
How to run it
- Put the real product into the team’s real workflow.
- Encourage honest logging of friction and bugs.
- Route feedback into the backlog.
- Prioritize fixes for issues felt repeatedly.
- Keep using it through each release.
Inputs and outputs
- Inputs: A usable product and a team willing to rely on it.
- Outputs: Experienced friction points, bug reports, and priorities.
Time and effort
Low. It rides on normal work.
Evidence and limitations
The team is a proxy for users, not a representative sample; builders know too much and share biases, so dogfooding complements but never replaces direct-user testing. See Evidence and limitations.
Tips and pitfalls
- Remember the team is not the user.
- Capture friction honestly, including your own.
- Do not let insider knowledge mask real problems.
Variations
Full dogfooding, limited internal beta, and friends-and-family testing.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Usability testing — Watch representative users attempt real tasks to find where the design helps or gets in their way.
- Customer feedback — Collect and analyze unsolicited feedback from the channels users already use.
- Design QA — Check the built product against the approved design to catch implementation drift before release.
