Engage Users Early

Early user engagement means getting feedback from real users while you’re still in the planning phase, before significant resources are spent on development. It’s much easier and cheaper to change your plans than to rebuild something that doesn’t work.

This isn’t about asking users what they want. It’s about testing whether your planned approach actually helps them accomplish their goals. The whole point of our process is that we engage with users as early as possible to confirm our assumptions based on research.

Early engagement validates that your structure makes sense to users, your scope addresses their priorities, and your overall approach aligns with how they think about their tasks.

Testing Whatever You Have

You don’t need wireframes, prototypes, or polished designs to start engaging users. Whatever planning materials you’ve created—site maps, navigation iterations, content groupings—can be tested to validate your assumptions before moving forward.

The key is testing your foundational decisions when they’re still easy to change. Use simple materials and focus on whether your planned approach supports user goals and mental models.

Present your draft site map or navigation structure to users and ask them to explain where they would look for specific information. This reveals whether your organizational logic makes sense to people outside your team.

Give users realistic scenarios and ask them to trace through your proposed structure. Where would they start? What path would they follow? Their responses validate whether your hierarchy matches user expectations.

Use tree testing methods even with rough site maps. You can test navigation concepts using simple text lists that reflect your proposed structure without any visual design.

Take the results from your card sorting sessions and test them with additional users. Present the groupings and category names that emerged from card sorting to see if they resonate with a broader user base.

Ask users what they expect to find in each category based on the labels. This helps validate that the terminology from card sorting actually communicates effectively to your target audience.

Test edge cases by asking users where they would look for content that doesn’t obviously fit into your main categories. This reveals gaps in your organizational scheme.

Present your planned scope and feature list to users in the context of their actual tasks. Ask which capabilities would be most valuable for accomplishing their goals and which seem less important.

Use simple lists or brief descriptions rather than detailed specifications. Focus on whether your scope priorities align with user priorities rather than specific implementation details.

Validate your scope boundaries by asking users about functionality you’ve excluded. Do they expect features you’ve decided not to include? Their reactions help confirm scope decisions.

Simple Validation Methods

These lightweight methods help validate planning decisions without requiring significant time or resource investment. Use them to test core assumptions before developing more detailed solutions.

Show users your site map, navigation labels, or content categories and ask for their immediate reactions. What feels clear? What’s confusing? First impressions often reveal whether your approach aligns with user expectations.

Ask users to explain what they think each category or section contains based on the label alone. Mismatched expectations indicate labeling problems that should be addressed before implementation.

Give users realistic scenarios and ask them to describe how they would navigate through your proposed structure to complete the task. Listen for hesitation, confusion, or unexpected paths.

Document where users feel confident versus where they’re unsure. These patterns help identify strong elements of your structure and areas that need refinement.

If you have multiple organizational approaches under consideration, present them to users and ask which feels more intuitive for their tasks. This helps choose between competing structural options.

Focus the comparison on task completion rather than visual preferences. Which approach would better support their actual work or information needs?

Ask Yourself

Early engagement with planning materials requires focusing on fundamental questions rather than design details:

  • Does my proposed structure match how users think about this content?
  • Can users predict where to find information based on my category names?
  • Do my scope priorities align with what users actually need to accomplish?
  • What assumptions am I making that users are contradicting?

Test your core organizational and strategic decisions before investing in detailed design work.

Moving to Build Phase

With validated structure, confirmed scope, and user-tested organizational decisions, you’re ready to move from planning into building your solution. Your early user engagement has provided the foundation for confident design and development decisions.

During the build phase, you’ll continue engaging users but shift focus from validating foundational decisions to testing specific implementations and interactions. The planning work you’ve completed provides a solid foundation for building something users actually need and can successfully use.

The Build Phase
sitemap