Requirements Gathering and Prioritization: The LuminTech Case Study
A step-by-step guide to identifying high-impact features, aligning them with user needs, and accelerating business value.
Today, we continue our case study at LuminaTech with a focus on requirement gathering.
To recap, we've already completed a stakeholder analysis—one of the most critical steps in any project.
If you missed it, all related articles are available in our Knowledge Hub.
Now, let’s dive deep into requirements analysis—where we translate insights into clear, actionable needs that drive the right solutions.
🧠 Why It Matters
Gathering requirements isn’t just about taking notes in meetings—it’s about understanding real needs, uncovering hidden value, and making sure the right problems get solved.
Great business analysts use structured elicitation techniques (like interviews, workshops, and journey mapping) to uncover needs, and prioritization frameworks to decide what should be built first.
In LuminaTech’s transformation from product sales to a subscription model, getting this step right meant aligning customer demand, business goals, and technical capacity.
📌 Context: LumiGlow Subscription Rollout
As part of LuminaTech’s evolving strategy, which we explored previously, the company began transitioning to a recurring revenue model in June 2025.
Now, as the Business Analyst, it’s your job to lead this transformation—by uncovering, refining, and prioritizing the requirements that will make it possible.
From product features to user experience to internal operations, your work will shape the foundation of this new business model.
🎯 How We Gathered Requirements
To build a complete and accurate picture of what’s needed, you should leverage multiple information sources. Here are the key channels we used in our case:
Stakeholder Interviews – You should conduct interviews with internal stakeholders. In our case, that included Product, Support, and the CEO, each offering unique perspectives on priorities and pain points.
Customer Surveys – You should design focused surveys. In our case, we engaged a pilot customer group to gather insights on their current experience and expectations.
Competitor Analysis – You should study your competitors. In our case, we analyzed key players in the market to identify feature gaps, pricing strategies, and positioning.
Support Ticket Mining – You should dig into historical support data. In our case, we reviewed support tickets to uncover recurring user complaints and areas of friction that needed attention.
Techniques You Should Apply to Shape and Validate Requirements
Once you’ve gathered input from your discovery channels, the next step is to make sense of it—to turn raw insights into structured, prioritized requirements. In our case, we applied several techniques to help synthesize the data, align stakeholders, and test early ideas:
User Journey Mapping – You should visualize how users interact with the current and future system across touchpoints. This helped us identify pain points, gaps, and opportunities in the customer experience.
“As-Is vs. To-Be” Workshops – You should facilitate collaborative sessions with stakeholders to define how things work today versus how they should work tomorrow. These workshops are critical for aligning expectations and uncovering hidden dependencies.
Collaborative Whiteboarding in Miro – You should use real-time digital whiteboarding tools. In our case, Miro was essential for visualizing ideas, mapping flows, and encouraging open collaboration—especially with distributed teams.
Quick Prototyping in Figma – You should bring concepts to life visually, even at an early stage. We used Figma to create lightweight prototypes that helped validate ideas quickly and gather immediate feedback from both users and stakeholders.
✅ Sample Requirements List for Subscription MVP
Below is our suggested list of the most critical and frequently requested features, based on insights from the initial requirements gathering phase:
SUB-001 – In-App Subscription Management
Users can view, modify, and cancel their subscription directly in the mobile app. (High value / Medium effort)
SUB-002 – Email Notifications for Subscription Events
Confirmation emails for start, renewal, cancellation, and failed payment. (High value / Low effort)
SUB-003 – Payment Method Update
Ability to update payment information within the mobile app. (High value / Medium effort)
SUB-004 – Pause Subscription
Temporarily suspend service (e.g., during vacation). (Medium value / Medium effort)
SUB-005 – Family Sharing / Multi-Device Access
Allow multiple household users to access the same subscription. (Medium value / High effort - phase 2)
SUB-006 – Loyalty Points System
Gamify usage with redeemable points. (Low value / High effort – deferred)
SUB-007 – Subscription Analytics Dashboard (Admin)
Internal dashboard to track active users, cancellations, revenue. (Medium value / Medium effort)
SUB-008 – Localized Pricing Based on Country
Adjust subscription pricing automatically based on user location. (High value / High effort – phase 2)
🧮 How We Prioritized
Now that the requirements have been gathered, it’s time to move into prioritization. For this, we applied a hybrid approach that combined two complementary methods:
MoSCoW Framework – Categorizing features as Must, Should, Could, or Won’t to define criticality and scope boundaries.
Value vs. Effort Matrix – Visualized in Miro, this helped us map features by impact and implementation effort, making it easier to identify quick wins and long-term investments.
✍️Tip: This format helps quickly identify:
Quick Wins (High value, Low effort): e.g., SUB-002
Strategic Investments (High value, High effort): e.g., SUB-008
Deferred or Low Priority Items (Low value, High effort): e.g., SUB-006
With our requirements now defined and prioritized, we can focus on the MVP scope. Here are the key areas selected for the initial release:
✅ Must-Haves – Core features essential for launch:
SUB-001: In-App Subscription Management
SUB-002: Email Notifications for Subscription Events
SUB-003: Payment Method Update🟢 Should-Haves – Important features that add value but are not critical on day one:
SUB-004: Pause SubscriptionSUB-007: Subscription Analytics Dashboard (Admin)
🔴 Could/Won’t for MVP – Lower-priority or higher-effort items, deferred to future phases:
SUB-006: Loyalty Points SystemSUB-005: Family Sharing / Multi-Device Access
SUB-008: Localized Pricing Based on Country
Now that we’ve walked you through the requirement gathering and prioritization phase, let’s summarize the key deliverables produced during this stage:
📦 Key Deliverables
Comprehensive Requirements Backlog – Maintained in Jira and documented in detail on Confluence.
Prioritization Matrix – Visualized in Miro to support collaborative decision-making.
Acceptance Criteria – Clearly defined for each requirement to guide development and testing.
Traceability Matrix – Links each requirement to its corresponding stakeholders and business objectives.
Executive Summary Presentation – Delivered as a PDF for the steering committee, capturing scope, priorities, and next steps.
💡 Final Thoughts
The real magic of requirement gathering isn’t just writing features down—it’s in asking the right questions, pushing past assumptions, and bringing clarity to complexity. This is where supercommunication becomes a critical skill for every Business Analyst—a concept we explored in detail in our previous article.
By combining stakeholder interviews, support ticket mining, competitor insights, and structured techniques like journey mapping and prototyping, we shaped a clear, value-driven backlog. One that aligns with LuminaTech’s strategic goals while staying grounded in user needs and implementation reality.
✍️ Coming Up Next
In the next article, we’ll walk through how we modeled the subscription process visually—from user interactions in the app to backend automation triggers—bridging the gap between business goals and technical execution.
Stay tuned.