How We Run Discovery — Effectively and on Time
You have real priorities. Your team has limited hours. Our discovery process is built around that reality, not around our convenience.
01 — Business-first communication
We talk business with your executives and switch to technical depth with your IT team — so no one sits through conversations that are not relevant to them, and everyone leaves informed.
02 — Respect for your calendar
We invite only the people each session actually needs, share agendas in advance, and keep every meeting purposeful. Your time is not a resource we burn casually.
03 — Remote or on-site — your call
Discovery sessions can run fully remote, at your premises, or as a hybrid. We adapt to your working model without any drop in quality.
04 — Visuals and prototypes
Abstract ideas become concrete quickly when we use diagrams, flowcharts, and clickable prototypes. Stakeholders understand faster and give better feedback when they can see, not just read.
05 — Constructive compromise
Different stakeholders hold different priorities. Rather than letting that stall things, we turn conflicting opinions into a coherent direction everyone can move forward with.
06 — Exact, unfiltered recording
We document what you tell us verbatim, keeping raw problems clearly separate from proposed solutions. No paraphrasing, no guesswork baked silently into the record.
07 — Action items after every session
Every meeting closes with clear owners, tasks, and deadlines. Nothing drifts because everyone knows exactly what comes next.
08 — Named backup contacts
We identify a secondary point of contact on your side before discovery begins, so a scheduling gap never halts progress mid-stream.
How Long Does Discovery Take?
Scope and complexity determine duration. Here are the typical windows our teams work within:
~3 weeks
For focused, straightforward projects
3 weeks – 2+ months
For large-scale or highly complex initiatives
Close, regular contact with your key stakeholders and subject-matter experts keeps things moving. We agree on a meeting rhythm that fits your team — daily, several times a week, or whatever works best. Sessions typically run one to two and a half hours, which keeps energy and output high.
“Business stakeholders have packed schedules. That is why every meeting starts with a pre-sent agenda so you can arrive prepared — not catching up. We use visual aids and prototypes throughout to keep decisions grounded in what the software will actually feel like, not abstract descriptions of it.”
— Head of Technology and Competency Development, INNERLUXES
The Three Main Phases of a Large-Scale Discovery
Below is a sample structure for a complex project. Smaller initiatives can compress the first two phases to roughly a week each.
Phase 1 — Initiation & Analysis (3 weeks)
- Kick-off sessions to align on goals, roles, timelines, and communication plans
- Working closely with your stakeholders to surface and elicit requirements
- Translating what we hear into documented business requirements
Interim deliverable: high-level feature list
Phase 2 — Design & Planning (3 weeks)
- Defining the project scope and core constraints
- Sketching out core user interfaces in wireframe form
- Defining technical requirements and selecting the right architectural approach
- Designing the software architecture
- Collaborative documentation review and sign-off with your stakeholders
Interim deliverable: UI wireframes
Phase 3 — Finalization (1 week)
- Ad-hoc sessions to close any gaps in the collected requirements
- Estimating implementation effort, timelines, and cost
Final deliverables:
Vision & scope document — objectives, target users, core functionalities
Technical vision document — tools, technologies, architectural decisions
Project roadmap — milestones, phases, key deliverables
Who Works on Your Discovery
Every discovery engagement is staffed with the right mix of experience. Here are the core roles we typically involve — and when.
Project Manager
5–8 years avg. · PMP, PSM I, PSPO I, ICP-APM
What They Do: Coordinates the team, manages client communication, prepares proposal and roadmap
When Involved: Throughout
Senior / Lead Business Analyst
5+ years in relevant industry
What They Do: Gathers requirements, prepares project documentation, creates wireframes and prototypes, conducts market research when needed
When Involved: Throughout
Solution Architect / Lead Developer
7+ years
What They Do: Translates business needs into technical requirements, assesses feasibility, identifies technologies, prepares architecture blueprints, flags potential risks
When Involved: Design & planning phase
Senior Developers
On demand
What They Do: Provide technical input on feasibility, develop prototypes or proofs of concept when required
When Involved: Design & planning phase; finalization (resource estimation)
Senior UX/UI Designer
On demand
What They Do: Prepares UX and UI concepts, user flow maps, and interface examples
When Involved: Design & planning phase
Additional specialists join on demand: compliance experts, database and network architects, data scientists, security engineers, and more — drawn from our team of 132+ in-house IT professionals.
Sample Discovery Engagement Options
No two projects are identical. These options are starting points, not rigid packages. We tailor the depth, composition, and deliverables to what your project actually needs.
Light — Quick-turnaround Discovery
Best for limited-scope projects or fast stakeholder buy-in. Approx. 3 weeks. Delivers a feature overview, feasibility report, project roadmap, and basic wireframes.
Basic — Foundations Discovery
Standard coverage for most projects. Adds deeper requirements documentation and an expanded wireframe set. Right-sized for teams who know what they want to build.
Technical — Architecture-Led Discovery
Goes deep on software architecture, detailed technical specifications, and one or more proofs of concept. Best when technology choices carry high long-term risk or cost.
Comprehensive — Full Discovery
End-to-end coverage: requirements, UX planning, architecture, PoCs, and a complete project roadmap. Suited for large or complex initiatives where ambiguity is costly.
Specialized — Discovery + Expert Services
Combines discovery with additional specialist input — compliance consulting, data science scoping, or security assessment — for regulated or technically complex domains.
Techniques We Use at Every Stage
Our business analysts draw from a broad toolkit of over 35 structured methods — choosing the right ones based on your project’s context, not a fixed checklist.
Requirements Gathering
- Stakeholder interviews
- Contextual observation
- Document and data analysis
- Business context diagrams
- Process modeling
Problem & Goal Analysis
- Root-cause mapping
- Job-to-be-done framing
- Outcome-to-feature traceability
- Constraint identification
Solution Ideation
- Collaborative workshops
- Rapid prototyping
- Concept sketching
- Competitive benchmarking
Evaluation & Prioritization
- MoSCoW prioritization
- Feasibility scoring
- Impact/effort mapping
- Risk-adjusted roadmapping
Discovery feeds directly into how we approach UX planning, UI design, scope estimation, cost planning, risk management, and team collaboration strategy.
More on How We Work
Discovery Phase – Q&A
The discovery phase is a structured pre-development engagement where INNERLUXES works with your stakeholders to gather requirements, define scope, design the technical architecture, create UX wireframes, and produce a project roadmap — giving every team member a shared, unambiguous picture of what will be built and how.
Duration depends on scope and complexity. Focused, straightforward projects typically complete discovery in approximately three weeks. Large-scale or highly complex initiatives can take from three weeks to two months or more.
Core roles include a Project Manager (5–8 years average experience), a Senior or Lead Business Analyst (5+ years in relevant industry), and a Solution Architect or Lead Developer (7+ years). Senior developers and a Senior UX/UI Designer join on demand during the design and planning phase. Additional specialists are available from our team of 132+ in-house IT professionals.
Final deliverables include a Vision and Scope document (objectives, target users, core functionalities), a Technical Vision document (tools, technologies, architectural decisions), and a Project Roadmap (milestones, phases, key deliverables). Earlier phases also produce a high-level feature list and UX wireframes.
Yes. Discovery sessions can run fully remote, on-site at your premises, or as a hybrid — whichever model fits your team’s working style, without any drop in quality or output.