Direction And Planning practice questions

Focus on value

Why it fails: While important, 'Focus on value' ensures everything links to value, but identifying bottlenecks specifically relates to optimization.

Think and work holistically

Why it fails: Holistic thinking ensures end-to-end perspective, but active elimination of waste is optimization.

Progress iteratively with feedback

Why it fails: Iterative progress deals with breaking work down, not directly analyzing flow efficiency.

Isolating executive leadership from operational teams to maintain top-down control.

Why it fails: Isolating leadership prevents the bidirectional goal translation that cascading requires, so business units never receive contextualised objectives. It is tempting as a governance model for preserving executive authority over strategic direction, which suits small organisations where leaders set strategy and delegate execution directly.

Relying strictly on informal communication without documented metrics.

Why it fails: Informal communication without documented metrics gives no traceable linkage between enterprise goals and unit objectives, so progress cannot be measured or corrected. It is tempting because informal channels do accelerate early alignment in small, co-located teams where everyone already shares context.

Allowing individual departments to create strategies completely independent of the enterprise.

Why it fails: Fully independent departmental strategies break the vertical alignment that cascading exists to create, producing goals disconnected from the corporate vision. It is tempting because autonomous unit-level planning genuinely suits decentralised firms where each division owns its own market and profit-and-loss accountability.

An annual financial balance sheet audited by external accountants.

Why it fails: Value stream planning produces a future-state value stream map with improvement actions, not financial statements. A balance sheet is an accounting artefact from financial reporting cycles, so it is tempting only if the term 'value stream' is confused with monetary value flows.

A physical floor plan of the server room architecture.

Why it fails: The exercise outputs a value stream map showing information and material flow, lead time, and process steps, not a physical layout. A floor plan belongs to facilities or data-centre design work, which is tempting when 'stream' is misread as physical infrastructure.

A list of software bug tickets assigned to junior developers.

Why it fails: Value stream planning identifies flow impediments and improvement opportunities at the process level, not individual defect tickets. Bug backlogs come from development tracking tools, which is tempting because both concern waste, but the exercise operates on end-to-end flow, not task assignment.

To enforce daily compliance checklists.

Why it fails: Daily compliance checklists are operational controls executed by staff, not statements of organisational direction. A mission statement expresses enduring purpose and scope; checklists enforce procedural adherence, so this option confuses tactical governance with strategic intent.

To outline a 20-year inspirational future state.

Why it fails: A mission statement defines the organisation's present purpose and core reason for existing, not a distant future state. Outlining a 20-year inspirational future state describes a vision statement, which is the correct choice when the scenario asks where the organisation aspires to be long-term.

To map out software deployment pipelines.

Why it fails: Software deployment pipelines belong to DevOps tooling and CI/CD configuration, not strategic direction. A mission statement articulates the organisation's enduring purpose and reason for existing, so pipeline mapping addresses an operational concern unrelated to this question.

Eliminate the security compliance team entirely to speed up delivery.

Why it fails: Removing the compliance team eliminates the control that satisfies regulatory obligations, converting delay into unmanaged risk rather than removing the handoff friction. It is tempting because fewer handoffs shorten lead time, and that would be correct only if compliance duties could be fully automated or absorbed elsewhere.

Increase the number of approval sign-offs to ensure absolute compliance.

Why it fails: Adding sign-offs lengthens the queue and increases wait time, directly worsening the handoff delay the value stream revealed. It is tempting because extra approvals appear to strengthen compliance, and that would be correct in a regulated context where evidence of independent review is contractually mandated.

Isolate the development team from the security team to avoid interpersonal conflicts.

Why it fails: Isolating the teams preserves the handoff and adds communication barriers, so the delay persists and compliance evidence weakens. It is tempting because separating groups appears to remove friction, and that would be correct if the two teams genuinely had no shared deliverables or dependencies.

Postponing operational planning until the digital strategy is fully complete across all sectors.

Why it fails: Delaying planning until the strategy is fully complete leaves operations unaligned during the transition and stalls delivery. It appeals as a way to avoid rework, and would be correct if the strategy were genuinely undefined and no interim direction existed.

Focusing exclusively on reducing IT operational costs regardless of digital goals.

Why it fails: Cost reduction alone ignores digital transformation objectives, so operational plans cannot demonstrate support for the new direction. It appeals when budgets are tight, and would be correct if the strategy itself prioritised IT cost optimisation over transformation outcomes.

Allowing each team to choose their own metrics without executive oversight.

Why it fails: Unsupervised team-chosen metrics break the line of sight between operational plans and enterprise strategy, so plans cannot be verified as supporting the transformation. It appeals as empowerment, and would suit autonomous squads with pre-agreed strategic guardrails.

Delegating all strategic planning entirely to frontline technicians.

Why it fails: Frontline technicians lack the strategic context and authority to translate corporate objectives into coordinated tactical plans, so cascading breaks down entirely. Delegation suits operational execution tasks within an established plan, not the formulation of strategy itself.

Top-down directive enforcement without performance measures.

Why it fails: Top-down directive enforcement without performance measures gives no feedback loop, so tactical plans cannot be tracked, adjusted or aligned to objectives. It would suit a compliance-driven mandate where directives alone suffice, not a strategy cascade requiring measurable execution.

Discarding long-term plans in favor of daily ad-hoc firefighting.

Why it fails: Ad-hoc firefighting addresses immediate operational incidents and cannot carry strategic objectives downward into structured tactical plans. Reactive daily triage is appropriate for incident response or crisis containment, where priorities shift hourly rather than following a deliberate cascade.

Value stream map

Why it fails: A value stream map visualises material and information flow to identify waste, so it cannot state a future aspiration. It is tempting because it supports strategic improvement, and would be correct when analysing current-state processes and designing leaner future-state workflows within operations.

Operational plan

Why it fails: An operational plan covers short-to-medium-term activities, budgets and tactics, so it cannot articulate a long-term aspiration. It is tempting because it translates strategy into action, and would be correct when detailing the specific initiatives, timelines and resources needed to execute an already-defined strategic direction.

Mission statement

Why it fails: A mission statement defines the organisation's present purpose and core business, not its future intended state. It is tempting because mission and vision are often paired, and a mission statement would be correct when answering what the organisation does, for whom, and why it exists today.

Software licensing agreement

Why it fails: A software licensing agreement governs permitted use of a product, not organisational direction or planning priorities. It tempts because licensing constrains what technology may be deployed, but the strategic hierarchy's apex is the strategic plan, which licensing sits beneath as a procurement artefact.

Operational schedule

Why it fails: An operational schedule allocates day-to-day tasks and resources, translating plans into activity rather than setting direction. It tempts because schedules coordinate execution, but they derive from strategy; the hierarchy's top is the strategic plan or mission, which schedules serve.

Incident response runbook

Why it fails: An incident response runbook documents step-by-step recovery procedures for specific scenarios, sitting below strategy and policy. It tempts because runbooks guide operational response, but the top of the hierarchy is the strategic plan or mission statement, which runbooks implement rather than direct.

Immediately rewrite the enterprise vision statement to match current legacy limitations.

Why it fails: Rewriting the vision to match legacy limitations abandons the 15% retention objective rather than removing the data silos blocking real-time personalisation. It is tempting because vision statements should reflect achievable capability, and this would be correct if the strategy itself were demonstrably unrealistic rather than the integration architecture being the obstacle.

Outsource all customer interactions to a third party without fixing internal systems.

Why it fails: Outsourcing customer interactions leaves the CRM data silos intact, so real-time personalisation remains impossible and the retention target is unmet. It is tempting because outsourcing can rapidly add channel capacity, and it would suit a scenario where internal staffing or support coverage, not data integration, is the binding constraint.

Ignore the CRM limitation and advise marketing to adjust their expectations downward.

Why it fails: Advising marketing to lower expectations abandons the retention objective instead of resolving the data silos blocking real-time personalisation. Ignoring the constraint suits scenarios where the limitation is out of scope or immaterial, not one where it directly prevents the stated strategic outcome.

Focus solely on software development coding hours.

Why it fails: Coding hours capture only one activity within the stream, missing handoffs, approvals and rework that also consume cycle time. Measuring total effort per step across the whole value stream is what exposes non-value-adding activity; coding-hour tracking suits developer productivity reporting instead.

Ask internal managers which tasks take the most time to complete.

Why it fails: Managers' time estimates reflect duration, not whether a step delivers customer value, so they mislabel long-but-wasteful activities as value-adding. Value-stream mapping walks the actual process with the people doing the work, timing each step and tagging delays, rework and handoffs as non-value-adding.

Assume all administrative sign-offs are critical value-add steps.

Why it fails: Treating every administrative sign-off as value-adding hides genuine waste, since approvals frequently add queue time without changing the product. Value is defined by what the customer would pay for, so each step must be tested against that; assuming sign-offs matter suits compliance auditing, not value-stream analysis.

Throughput

Why it fails: Throughput counts units completed per period, describing output rate rather than an idle interval. It is tempting because flow metrics feature heavily in value-stream mapping, and throughput would be correct if the question asked how much work a step delivers, but a queue where items wait is wait time.

Process time

Why it fails: Process time measures the duration work is actively being transformed, not the idle interval between steps. It is tempting because it is a core value-stream metric, and it would be the answer if the question asked how long a processing activity takes, but the described queue is wait time.

Lead time

Why it fails: Lead time spans from request to delivery across the whole value stream, encompassing both processing and waiting, so it does not name the idle interval itself. It is tempting because lead time includes queues, and it would be correct if the question asked total elapsed duration, but the specific delay is wait time.

By centralizing all operational decision-making within the governing board.

Why it fails: Concentrating every operational decision in the governing board removes the delegated authority that lets operational teams act, producing exactly the friction described. Centralising decisions is tempting because it guarantees policy alignment, and it would be correct for a small organisation with no operational layer, not one protecting agility.

By enforcing strict sequential approvals for every minor daily task.

Why it fails: Requiring sequential sign-off for every minor daily task embeds approval gates directly into routine operations, which is the conflict the scenario asks to avoid. Strict approval chains suit high-risk, low-volume changes, so they are tempting where control matters most, but they stall the operational agility leadership wants preserved.

By eliminating all policies to maximize unconstrained agility.

Why it fails: Removing every policy leaves no governance layer to align with operational work, so direction ceases to exist rather than being reconciled with agility. Abolishing controls is tempting when policies are seen as blockers, yet it would only fit an organisation deliberately choosing zero oversight, not one balancing governance against operational freedom.

An automated password reset portal.

Why it fails: An automated password reset portal handles identity credential recovery, offering no framework for translating strategy into department-level projects. It is tempting because it is a familiar self-service IT tool, and would be correct for reducing helpdesk load by letting users reset forgotten passwords securely.

An incident management ticket queue.

Why it fails: An incident management ticket queue tracks faults and service requests, carrying no mechanism to cascade strategic objectives into departmental projects. It is tempting because ticketing systems already structure work and ownership, and would be correct for logging, prioritising and resolving operational incidents.

A physical hardware asset inventory spreadsheet.

Why it fails: A hardware asset inventory spreadsheet lists physical equipment and ownership, capturing no strategic objectives or project alignment. It is tempting because spreadsheets are flexible and widely used for planning, and would be correct for tracking device serial numbers, locations and warranty expiry.

By separating compliance into a completely disconnected annual audit cycle.

Why it fails: An annual disconnected audit leaves compliance unverified during delivery, so defects surface long after release and remediation becomes costly. Periodic external audits suit stable, slow-changing environments, not a value stream needing continuous evidence of control alongside rapid delivery.

By bypassing compliance requirements whenever speed is prioritized.

Why it fails: Bypassing compliance removes the controls the board explicitly requires, trading one half of the stated balance for the other. This approach would fit a scenario prioritising speed alone, but here regulatory obligations are non-negotiable, so compliance must be automated into the pipeline instead.

By requiring all code releases to undergo a mandatory 3-week manual review board.

Why it fails: A fixed three-week manual gate serialises every release, so compliance is enforced by delaying delivery rather than by automated controls, destroying the agility the board requires. Manual review boards suit low-frequency, high-risk changes, not continuous value stream flow.

Establishing global corporate mergers and acquisitions.

Why it fails: Mergers and acquisitions are strategic, long-horizon portfolio decisions, not the short-term tactical execution an operational plan covers. It is tempting because operational plans do address growth, but that growth is delivered within the year against existing products and markets.

Defining the 10-year organizational vision and core purpose.

Why it fails: A ten-year vision and core purpose belong to the strategic plan, which sets direction; the operational plan translates that direction into near-term actions. It is tempting because both documents reference the vision, but only the strategic plan defines it.

Formulating foundational enterprise values and ethics.

Why it fails: Foundational values and ethics are established at the strategic level, framing the organisation's enduring identity; operational plans implement them through specific annual activities. It is tempting because operational plans must align with those values, yet they do not formulate them.

Writing marketing copy for product brochures.

Why it fails: Value stream mapping charts the flow of work and information through delivery to expose delays and waste; marketing copy is unrelated to process flow. It is tempting because mapping produces documentation, but the artefact maps steps, not promotional content.

Designing server network topologies and firewall rules.

Why it fails: Value stream mapping focuses on process steps and information flow from request to delivery, not infrastructure design. It is tempting because technical enablers appear as steps, but server topology and firewall rules belong to architecture, not value stream analysis.

Calculating annual employee salary bonuses.

Why it fails: Value stream mapping examines cycle time, queue time and handoffs across the delivery pipeline; salary bonus calculation is a finance activity outside its scope. It is tempting because both involve metrics, but the map targets flow efficiency, not compensation.

Collaborate and promote visibility

Why it fails: Collaboration is relevant, but iterative feedback loops are the hallmark of feedback principles.

Keep it simple and practical

Why it fails: While simplicity is good, feedback loops specifically test feedback mechanisms.

Start where you are

Why it fails: Starting where you are means assessing existing processes and reusing what works before building anew; it does not address creating dialogue between strategy and operations. It is tempting because feedback loops build on current practice, and would be correct if the organisation were deciding whether to replace or retain existing tooling.

Board of directors charter

Why it fails: A board charter defines the board's governance authority, composition and duties, not departmental tactical objectives. It is tempting because charters are formal governing documents, which suits establishing oversight structures rather than the annual operating plan the stem describes.

Enterprise vision document

Why it fails: An enterprise vision document states long-term strategic direction and organisational aspirations, not tactical steps, resources or fiscal-year timelines. It is tempting because it does set departmental direction, but it would be the right artefact only when articulating multi-year strategy, whereas the stem demands an operational, time-bound plan.

Master value chain theory textbook

Why it fails: A value chain theory textbook explains academic frameworks, not an organisation's tactical steps, resources and timelines. It is tempting because value chain analysis informs strategic planning, which suits conceptual coursework rather than the operational annual plan the stem describes.

Increase the size of development batches to reduce test frequency.

Why it fails: Larger development batches increase work in progress and queueing before test, lengthening lead time rather than reducing the 80% test bottleneck. It is tempting because fewer test cycles appear to save effort, but batch size is the axis that governs flow, not test frequency.

Eliminate testing phases to accelerate service release.

Why it fails: Removing testing eliminates the quality gate that validates the 5G service, allowing defects to reach release rather than shortening the constraint. It is tempting because testing dominates lead time, yet the strategic intervention is to relieve that constraint through automation and flow, not delete it.

Outsource development while keeping testing manual and internal.

Why it fails: Outsourcing development while retaining manual internal testing leaves the 80% test constraint untouched and adds handoff delay. It is tempting because external capacity appears to accelerate delivery, but the bottleneck sits in testing, so offshoring build work does not shorten lead time.