FBTE34511 Chap.2 Client Discovery and Problem Framing
Client Discovery and Problem Framing
Client Discovery and Problem Framing converts a broad organisational ambition into a researchable challenge. The chapter distinguishes contextual evidence from background description, separates external push pressures from pull opportunities and protects the appraisal by keeping a preferred technology out of the problem statement.
A useful frame names the actor, current capability gap, consequence, desired change and scope. It also carries uncertainty honestly: a client belief is a hypothesis until operating evidence supports it. The completed frame should lead naturally into a systems map by identifying the actors, flows and decisions that need explanation.
What this chapter covers
- 01
Client discovery
- 02
Context evidence
- 03
PEST analysis
- 04
Push pressures
- 05
Pull opportunities
- 06
Problem boundaries
- 07
Research questions
Worked example · free
Reframe a request for a customer app
- 1Identify inconsistent return instructions and missing item condition evidence.
- 1Show consequences for recoverable products, planning and verified claims.
- 1State the required capability across customers, outlets and repair partners.
Key terms
- Push factor
- An external pressure that makes organisational response more urgent or necessary.
- Pull factor
- An external opportunity that makes an innovative response more attractive.
- Problem boundary
- The stated actors, processes, place and time included in the investigation.
Client Discovery and Problem Framing FAQ
How much organisational background should I include?
Include context that changes the problem priority, constraints, stakeholders or feasibility of a response. A company history or trend list that does not affect the decision uses space without strengthening the consultancy argument.
Can one issue be both a push and a pull factor?
Yes. A regulatory change can create compliance pressure while also rewarding organisations that develop stronger traceability. Explain the different strategic implications rather than forcing every observation into only one label.
What makes a problem statement too narrow?
A statement is too narrow when it assumes the answer, excludes important actors or treats a symptom as the cause. Keep enough scope to examine the mechanism while remaining specific enough that evidence and action can be identified.
How should I test the boundary of the problem?
Draft one narrower operational frame and one wider systemic frame alongside the proposed statement. For each version, note which evidence, actors, consequences and interventions enter or leave scope. Select the level that matches the client's decision while retaining dependencies that could defeat it. Explain why the boundary is useful, what it excludes and when new evidence would require it to be reopened.
This comparison exposes a frame chosen merely because it favours the team's preferred solution and gives the later systems map a defensible starting boundary.
Assessment move
Use an evidence funnel. Gather organisational and external observations, then write the implication of each one. Group those implications into pressures and opportunities, rank them by relevance and evidential strength, and choose the bounded gap that the report can address. Draft the problem without a technology noun. Add the actor, current condition, consequence, desired capability and limits of scope.
Finally, write one research question and identify which actors and flows the systems map must examine. Revise any sentence that reports a fact without explaining why it matters to the decision. Build a context ledger with four columns: observation, source, interpretation and consequence for the project. This stops a PEST scan becoming a list.
If a regulation, market trend or technology shift does not change urgency, constraint, stakeholder or option, it may not deserve space in the report. For every push factor, ask what minimum response it demands. For every pull factor, ask what opportunity it creates and which capability is needed to capture it.
Rank issues using direct connection to the brief, quality of evidence, consequence for affected groups and the organisation's ability to influence the outcome. Then separate symptoms from causes. Rising waste cost may be a symptom; unclear ownership, unsuitable design or missing recovery capacity may be mechanisms. Draw a short causal chain and note where evidence remains weak.
Interview statements should be labelled as perceptions until records or observation corroborate them. Test the frame by generating at least three possible responses. If only one answer fits, the statement probably contains a hidden solution. Rewrite technology nouns as capabilities, such as preserving identity, coordinating hand-offs or verifying condition. Add exclusions explicitly so the scope is credible.
State which material, actor, geography or lifecycle stage is outside the current investigation and why. Finally, draft the transition to systems analysis. Name the actors, flows, decisions and feedback that need mapping to explain the gap. A reader should understand why the next visual exists before seeing it.
Keep the final problem statement short enough to repeat accurately in the executive summary, roadmap and conclusion without changing meaning.
Working through Client Discovery and Problem Framing in FBTE34511? Sia is AskSia’s AI Management tutor — ask any FBTE34511 Client Discovery and Problem Framing question and get a clear, step-by-step explanation grounded in how FBTE34511 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.