Latest / 5 Minute UX / Prioritization Techniques: A Practical Guide
Transcript
- 0:07This lesson is Prioritization Techniques: A Practical Guide.
- 0:11Let's get started.
- 0:18Start by identifying the three selection factors: collaboration
- 0:21level, idea maturity, and domain knowledge. You need to determine
- 0:24if your process requires deep group engagement or a more
- 0:26analytical approach. This first check dictates which technique
- 0:29you will actually use. Next, evaluate idea maturity to see if
- 0:32you are sorting high-level concepts, mid-level features, or
- 0:34low-level details. The level of your ideas must match the method
- 0:37you choose to avoid confusion. Then check domain knowledge to
- 0:39gauge how much the team knows about the industry or
- 0:42technology. Once selected, you describe the three-phase
- 0:44execution workflow: prepare, facilitate, and document. Begin
- 0:47the prepare phase by gathering inputs and setting the
- 0:49environment with a physical whiteboard or digital tool. You
- 0:51then move to facilitate the group process by running the
- 0:54session and ensuring all voices are heard. If the process
- 0:56stalls due to conflicting opinions, you apply the KJ-
- 0:59Technique variation to reset the discussion. This specific
- 1:01recovery step helps you build consensus before moving to the
- 1:04final stage. Finally, document the priorities by creating a
- 1:06prioritized list or matrix that reflects the agreed-upon
- 1:08sequence. Validate the output so the team understands the
- 1:11rationale behind every decision made during the session. Use
- 1:14this completed prioritization document to immediately begin
- 1:16preparing for the full design effort. This direct transition
- 1:19ensures your prioritization work drives the next phase of your
- 1:21project forward.
- 1:27Here is the Fix on prioritization sessions! You
- 1:29just spent three sprints on a dashboard nobody opens because
- 1:32you skipped the prep work. Stop the bleeding. Prioritization is
- 1:35simply the bridge between messy ideas and a clear design plan.
- 1:37It forces your team to agree on what to build first before you
- 1:40waste a single hour of coding time. This is how you align
- 1:43resources with actual value. Start by gathering inputs.
- 1:45Collect the specific list of features, ideas, or requirements
- 1:48that need sorting right now. Do not skip this step. Then, select
- 1:51the method. Choose a technique like MoSCoW, RICE, or Kano that
- 1:53fits your collaboration level, idea maturity, and domain
- 1:56knowledge. You need the right tool for the job. Set the
- 1:58environment. Ensure the team has the tools required, whether that
- 2:01is a physical whiteboard for sticky notes or a digital
- 2:03collaboration tool. Now, run the session. Guide the team through
- 2:06the chosen technique while ensuring all voices are heard.
- 2:09What happens when you hit a wall? If the process stalls due
- 2:11to conflicting opinions, apply the KJ-Technique to reset the
- 2:14discussion. This variation helps you re-establish momentum and
- 2:17build consensus immediately. Do not let arguments freeze your
- 2:19progress. Finish by creating the prioritization document.
- 2:22Compile the results into a clear format, such as a prioritized
- 2:25list or matrix. Validate the output to ensure the team
- 2:27understands the rationale behind every decision. Finally,
- 2:30transition to design. Use the completed document to
- 2:32immediately begin preparing for the full design effort that
- 2:34follows. That is your Fix on prioritization sessions!
- 2:43Let's say you have a team gathered around a physical
- 2:45whiteboard or a digital collaboration tool, ready to
- 2:47tackle a messy list of features. Your first job is to run the
- 2:49session by guiding everyone through the chosen technique,
- 2:52ensuring all voices are heard and the criteria are applied
- 2:54consistently. You can't just throw ideas at the wall; you
- 2:56must actively manage the flow so the process stays structured.
- 2:59You'll inevitably hit a wall where conflicting opinions cause
- 3:02the momentum to stall completely. This is exactly when
- 3:04you apply a variation of the KJ- Technique to reset the
- 3:06discussion and re-establish momentum. Instead of arguing
- 3:08over individual items, you group similar ideas together to find
- 3:11common ground. This simple shift breaks the deadlock and helps
- 3:14the team see patterns they missed before. Once the dust
- 3:16settles, you must focus on building consensus by achieving
- 3:18a common understanding among stakeholders before moving to
- 3:21documentation. It doesn't matter if everyone loves every item,
- 3:23but they must agree on the sequence and the rationale
- 3:25behind it. You're looking for a shared mental model that
- 3:28validates the output and confirms the agreed-upon
- 3:30priorities. Now you take that alignment and create the
- 3:32prioritization document, compiling the results into a
- 3:34clear format like a prioritized list or a matrix. This document
- 3:37isn't just a record; it is the contract that tells the team
- 3:39exactly what to build next. You validate this output to ensure
- 3:42it reflects the decisions made, then use it to immediately begin
- 3:44preparing for the full design effort. This transition ensures
- 3:47your prioritization work directly fuels the next phase
- 3:49without losing any of that hard- won clarity.
- 3:57Pause and think about your last project where the team got stuck
- 4:00in a loop of conflicting opinions. That stalemate happens
- 4:02when you forget to apply the KJ- Technique variation to reset the
- 4:05discussion and re-establish momentum immediately. You need
- 4:07to use that specific tool to break the deadlock before you
- 4:10can move forward with any real progress. Now, focus on
- 4:12creating the Prioritization Document by compiling your
- 4:14results into a clear format like a prioritized list or matrix.
- 4:17This tangible output serves as the contract for what will be
- 4:20designed and built in the upcoming phases of your project.
- 4:22Without this specific document, your team lacks the shared
- 4:24understanding needed to execute the work effectively. Next, you
- 4:27must validate the Output to ensure the document reflects the
- 4:30agreed-upon sequence and the team understands the rationale.
- 4:32This step confirms that everyone sees the same logic behind the
- 4:35decisions, preventing confusion before you start building. If
- 4:37the team doesn't grasp the reasoning now, the design phase
- 4:40will face unnecessary friction and delays. Finally, use the
- 4:42completed prioritization document to immediately begin
- 4:45preparing for the full design effort that will follow. This
- 4:47direct transition ensures your prioritization activities remain
- 4:50linked to the actual work, avoiding the pitfall of an
- 4:52isolated exercise. You have now executed the full workflow from
- 4:55preparation to documentation, closing the loop on your design
- 4:57strategy.
- 5:01Welcome to The Take. I'm joined by a fellow practitioner and
- 5:04together we're going to dig into Prioritization Techniques: A
- 5:07Practical Guide — what it means in practice and what's worth
- 5:10remembering.
- 5:11[HOST] That warning about skipping prep work really hit
- 5:14home, especially the part about wasting three sprints on a
- 5:17dashboard nobody uses. [LEARNER] It's terrifying how often we
- 5:20jump straight to voting on features without first checking
- 5:23if our team actually shares the same mental model. [HOST] And
- 5:26that's exactly why the lesson insists on matching the
- 5:28technique to idea maturity before you even set up the
- 5:31whiteboard. [LEARNER] I've seen teams use RICE on vague
- 5:34concepts, and the whole exercise collapses because the data
- 5:36inputs are just guesses. [HOST] When that happens, the script
- 5:39suggests pivoting to the KJ- Technique variation to reset the
- 5:42discussion and find patterns instead of arguments. [LEARNER]
- 5:45That grouping step is usually the only way to break the
- 5:48deadlock when stakeholders are fighting over individual items.
- 5:51[HOST] It forces the room to look at the forest rather than
- 5:54getting stuck arguing about a single tree. [LEARNER] Speaking
- 5:57of patterns, I'm wondering if AI can actually help us identify
- 6:00those clusters faster than we can with sticky notes. [HOST] It
- 6:03could certainly draft the initial groupings, but the real
- 6:06value is in the debate that happens when the team challenges
- 6:09the AI's logic. [LEARNER] True, because the consensus comes from
- 6:12the friction, not just the output, so the tool can't
- 6:15replace the facilitator's role. [HOST] Exactly, and if we skip
- 6:18that validation step, the prioritization document becomes
- 6:20a contract nobody actually agrees to. [LEARNER] That
- 6:23document needs to feel like a shared victory, not just a list
- 6:26imposed by the most vocal person in the room. [HOST] Once you've
- 6:29that alignment, the transition to design happens immediately
- 6:32because the rationale is already baked into the sequence.