Latest / 5 Minute UX / Site Map Elements (Pages, Pagestacks, Decision Points)
Transcript
- 0:08This lesson is Site Map Elements (Pages, Pagestacks, Decision
- 0:12Points). Let's get started.
- 0:21The strategic choice between static pages, page stacks, and
- 0:24decision points defines how users navigate and how
- 0:26stakeholders understand the product's logic. This isn't
- 0:28merely structural; it's a move that balances clarity against
- 0:31the complexity of user flows. Experienced practitioners use a
- 0:34specific heuristic: map the risk, not just the content. This
- 0:36forces you to look beyond the inventory of pages and ask what
- 0:39the user is actually doing. When the goal is exploration,
- 0:41static pages work best for informational sites. But if the
- 0:44user must follow a set path to succeed, page stacks are optimal
- 0:47for task-based flows. Decision points become essential when
- 0:49user paths diverge based on choices. This is critical when
- 0:52usability issues carry severe consequences, like safety risks
- 0:54or lost sales. Teams often default to static pages,
- 0:57rationalizing that they can add the logic later. This leads to a
- 1:00disconnect where critical decision points remain invisible
- 1:02until development is complete. By identifying these three core
- 1:05site map elements, you can select the appropriate
- 1:07representation. You'll describe the specific project conditions
- 1:10that favor each structure. Then, you'll apply the 'Map the
- 1:12Risk' heuristic to determine the optimal map structure. This
- 1:15prevents stakeholder gridlock and ensures your testing covers
- 1:17the paths where users actually get stuck.
- 1:25The sequence begins by reading specific signals in your project
- 1:28environment. You need to identify the conditions that
- 1:30favor each site map representation. This moves you
- 1:32away from guessing and toward evidence-based structure.
- 1:35Stakeholder disagreement is a powerful signal. When teams
- 1:37argue about design direction, friction blocks progress.
- 1:39Switching to a decision-point model resolves this because
- 1:42seeing is believing. Visualizing the logic turns opinion into
- 1:44evidence. This breaks the gridlock and aligns the team.
- 1:47Task complexity points directly to page stacks. If users must
- 1:49complete a series of steps, linear progression works best.
- 1:52Think of a corporate training course or a checkout flow. The
- 1:54goal is task completion, not browsing. Page stacks help you
- 1:57pace content for comprehension. This ensures users don't get
- 2:00overwhelmed by information. High-stakes consequences demand
- 2:02rigorous mapping of decision points. Consider a healthcare
- 2:05app calculating medication dosage. A wrong input here isn't
- 2:07just bad UX; it's dangerous. You must map every branch to catch
- 2:10safety risks. The cost of a missed path is too high to
- 2:12ignore. Data availability changes how you validate your
- 2:15choices. If you can test options against real user behavior, do
- 2:17it. This prevents decisions based on the Highest Paid
- 2:19Person's Opinion. You rely on facts, not hunches. This keeps
- 2:22your map grounded in reality. Apply the Map the Risk heuristic
- 2:25to determine the optimal structure. Ask three questions.
- 2:27Is the outcome binary or linear? Use page stacks. Are there
- 2:30critical branching points with risk? Use decision points. Is
- 2:32the goal exploration? Use static pages. This heuristic forces you
- 2:35to look beyond content inventory. You focus on what the
- 2:37user is actually doing. This prevents rationalizing the wrong
- 2:40choice for simplicity.
- 2:47Let's say you are building a medication dosage calculator
- 2:50where a wrong input could lead to dangerous outcomes. You don't
- 2:52just list the screens; you explicitly map out where a user
- 2:55might make a critical error. This is the moment you choose
- 2:57Decision Points because a user choice leads to significantly
- 3:00different risks. Now, imagine you are designing an online
- 3:03learning module where new employees must follow a set path
- 3:05to succeed. The outcome is binary or linear, so you use
- 3:08Page Stacks to represent that specific flow. This approach
- 3:10breaks the content into manageable chunks that are paced
- 3:13for comprehension without overwhelming the user. Consider
- 3:15a corporate website where the primary goal is exploration
- 3:18rather than task completion. If the user is browsing for
- 3:20information without a specific task, you use Static Pages to
- 3:23establish a basic inventory. This method works best when your
- 3:26project timeline is short and you need clarity without
- 3:28modeling complex interactions. The core principle here is to
- 3:31look beyond the inventory of pages and ask what the user is
- 3:33doing. You must also ask what happens if they make the wrong
- 3:36choice to truly map the risk. Visualizing this logic moves the
- 3:39conversation from opinion to evidence and prevents the "we
- 3:41can add the logic later" trap. When stakeholders disagree on
- 3:44the design direction, seeing the branching logic often resolves
- 3:47disputes because seeing is believing. You avoid the cost of
- 3:49the Highest Paid Person's Opinion by using data to
- 3:51validate the chosen map structure. This heuristic forces
- 3:54you to identify critical branching points before
- 3:56development begins. By applying the "Map the Risk" heuristic,
- 3:59you select the appropriate site map element based on project
- 4:01constraints. You now know how to apply this decision framework to
- 4:04determine the optimal map structure for any scenario. This
- 4:07ensures your map serves as a dynamic model of user behavior,
- 4:09not just a static list.
- 4:17Pause and think about your last project where a simple page map
- 4:20failed to capture the real user risk. Did you default to static
- 4:23pages because they were easy, or did you actually map the logic?
- 4:26This is where you apply the heuristic to map the risk, not
- 4:28just the content. Consider a healthcare app building a
- 4:31medication dosage calculator. If you treat this as static pages,
- 4:34you bury critical safety warnings deep in the code until
- 4:36a fatal error occurs. Instead, you must use decision points to
- 4:39visualize exactly where a user might skip a warning and cause
- 4:42harm. Seeing this branching logic moves the conversation
- 4:44from opinion to hard evidence. Now contrast that with a
- 4:47corporate training course for new employees. Here, the goal is
- 4:49a linear progression through lessons, so you need page stacks
- 4:52to define that specific task flow. If you miss this
- 4:54distinction, you risk stakeholder gridlock or
- 4:56ineffective testing that never uncovers where users get stuck.
- 4:59Ask yourself: is the outcome binary, or is it a linear path?
- 5:08A frequent error is defaulting to static pages because they are
- 5:11easier to draw, rationalizing that logic can be added later.
- 5:14This leads to a disconnect between your map and the actual
- 5:16user experience, leaving critical decision points
- 5:19invisible until development is complete. You might avoid the
- 5:21immediate friction of mapping complex flows, but you will face
- 5:24much higher costs when safety warnings or revenue logic are
- 5:27buried in code. Watch out for stakeholder gridlock when you
- 5:29skip mapping decision points in high-stakes environments.
- 5:32Without visualizing the branching logic, teams remain
- 5:34stuck in political debates because the facts of the user
- 5:37flow are not visible. Seeing the consequences of different paths
- 5:39is often the only way to move from opinion to evidence. To
- 5:42prevent this, review your current project's user flows and
- 5:45apply the Map the Risk heuristic to validate your structure. Ask
- 5:47yourself if the outcome is linear, if there are critical
- 5:50branching points, or if the goal is simple exploration. This
- 5:53forces you to look beyond the inventory of pages and determine
- 5:55what the user is actually doing when they make a wrong choice.
- 5:58That brings us full circle: your site map must reflect the logic
- 6:01of the product, not just the list of its parts. By mapping
- 6:04the risk, you ensure your design serves the user's needs while
- 6:06protecting your team from costly oversights.
- 6:11Welcome to The Take. I'm joined by a fellow practitioner and
- 6:14together we're going to dig into Site Map Elements (Pages,
- 6:17Pagestacks, Decision Points) — what it means in practice and
- 6:19what's worth remembering.
- 6:22[HOST] The moment we realized we were mapping inventory instead
- 6:25of risk, the whole project dynamic shifted. [LEARNER]
- 6:27Exactly, and that shift is hard to sell when stakeholders just
- 6:30wanna see a list of pages. [HOST] That's where the friction
- 6:33actually tells you you need to visualize the decision logic,
- 6:36not just the content. [LEARNER] I've seen teams default to
- 6:39static pages because they're easier to draw, even when the
- 6:42flow is clearly branching. [HOST] It's the classic "we can
- 6:45add the logic later" trap that costs us three sprints before we
- 6:48find the fatal gap. [LEARNER] I wonder if AI tools are making
- 6:51this trap worse by auto- generating page lists before we
- 6:54even define the risk. [HOST] That's a real danger, because
- 6:57the model will happily generate a static map unless we force it
- 7:00to identify the branching points. [LEARNER] So we have to
- 7:03prompt it to find the safety warnings or the financial logic
- 7:06before it starts drawing boxes. [HOST] Precisely, otherwise we
- 7:09just get a faster version of the same disconnected inventory
- 7:12list. [LEARNER] It forces us to be the ones defining the "Map
- 7:15the Risk" heuristic before the AI even touches the canvas.
- 7:17[HOST] And once you see those decision points visualized, the
- 7:20political debate about the right path usually evaporates.
- 7:23[LEARNER] Seeing the consequences of a wrong choice
- 7:26is the only thing that moves the conversation from opinion to
- 7:29evidence. [HOST] We stop guessing where users get stuck
- 7:32and start designing for the actual danger in the flow.