CROSS-DOMAIN PATH
Product and end-to-end thinking
A path across modeling (B), judgment (C), and delivery (D): start from the user’s problem, judge whether it is worth doing, and trace whether action produced a result.
Each question below still belongs to one capability. The path only gathers them in reading order.
1. B · Business understanding and domain modeling57
- Besides your product, what else could users do to get the same job done? What does each alternative compete for, and when is it actually the better choice?
- A premium service tier earns more revenue but consumes more human support, and renewal has not improved. How would you determine whether it creates incremental value?
- A product is sold once but requires long-term support and upgrades. Revenue is growing while the service queue accumulates. How would you decide whether these sales still create value?
- Pick a module you own. Explain who it serves, what input it takes, what output it provides, and follow the user task through to the business result.
- When you explain a business, how do you first lay out the whole and then the position and value of the part you own within it? How does someone without a whole-picture view tell it, and what is the difference?
- The business says data must be real time, but no one can explain the cost of a fifteen-minute delay. How would you decide the architecture and freshness target?
- A user consented to product analytics, then withdrew consent. Derived metrics already reached reports, experiments, and model-training data. How would you model consent state, purpose scope, and propagation?
- A support ticket can be reopened when a customer provides new evidence and may be split into follow-up work. How would you model states and events so closure, reopening, and splitting remain traceable?
- Enterprise contracts specify first response, service restoration, and final resolution times, each with different pause conditions. Support tracks one SLA timer, causing disputes. How would you model this?
- Map the area you have owned over time: what users are trying to do, where the main process obstacles are, what your module can influence, and what is outside its control.
- Write a one-page product overview for someone who just joined. How would you mark which statements are fact, which are inference, and which are simply unanswered questions?
- Where does your project sit in the wider business? Who gives it input, who uses its results, and who is affected if it is late or wrong?
- An enterprise product charges a monthly subscription, overage usage, and a minimum-spend true-up. How would you define billing periods, usage attribution, price effective time, and invoice explanations so a customer can reconcile the charges?
- A promotion increases sales volume, but new customers’ first orders remain unprofitable after discounts, channel fees, and fulfillment costs. How would you isolate the loss and decide whether to change the offer threshold, audience, channel, or stop the promotion?
- A new plan makes more users willing to try the product, but some customers who would have bought a higher-priced plan switch to the cheaper option. What commercial model and observation window would you use to judge whether the plan portfolio creates incremental value?
- Map the value flow among users, suppliers, the platform, and payers in a two-sided marketplace you know. Explain how value and responsibility change when a service is not fulfilled.
- A new industry or regulatory requirement forces a product workflow change. How would you trace from the requirement to affected participants, value-chain steps, business commitments, and internal systems?
- After a promotion ends, operations considers the campaign complete, product sees orders still being fulfilled, and finance says settlement is not yet possible. How would you define each party’s objects, states, and state transitions?
- The same person may encounter a product through ads, an agency, a partner, and a self-serve channel, and different parties may pay. How would you distinguish customer, buyer, user, and acquisition touchpoint in the business model?
- An enterprise customer has multiple organizations, departments, and members, and a member may act for different organizations. When designing customer activity analysis, how would you define the grain and relationships among customer, account, organization, and user?
- Business units use an “active customer” metric, but some define it by payment, others by usage, and others by likelihood to renew. How would you decide which definitions should be standardized and which should remain distinct concepts?
- A supplier API replaces one “delivered” status with “dispatched” and “received,” but historical data has no basis for distinguishing them. How would you update the domain model, external contract, and related reporting?
- The team plans to enter an adjacent market where users, payers, and fulfillment parties differ. How would you map the value chain and determine whose problem the product should solve first?
- Teams define “done,” “awaiting acceptance,” and “paused” differently, distorting roll-up data. How would you design a shared state model and transition rules?
- A user can belong to several organizations and hold different roles in each. How would you model identity, membership, and permissions without conflating accounts with business roles?
- Marketplace transactions keep growing, but buyers wait longer, sellers cancel more often, and subsidy spending rises. How would you describe the exchange of value and constraints across participants, then decide whether growth reflects better matching or one-sided subsidy?
- An order moves through created, awaiting confirmation, processing, partially fulfilled, canceled, and refunded states; different pages and services interpret “complete” differently. How would you model state, events, and valid transitions so each client does not invent its own meaning?
- Enterprise customers expect a weekday response, while individual users expect self-service at any time; the team plans to standardize one support workflow. How would you analyze customer needs, issue urgency, service commitments, and delivery costs?
- An enterprise customer uses one contract for several departments; employees may work across departments, and administrators may operate on behalf of multiple accounts. How would you distinguish organizations, contract accounts, individual identities, memberships, and authorization scope?
- A cross-team project launches on schedule, but user feedback, operating costs, and data corrections remain; the project team is about to disband. How would you model product, platform, operations, and project responsibilities after delivery?
- A product feature is configured by customer contract, adjusted by experiment group, and constrained by regional rules; analysts need to explain which combination shaped a user's experience. How would you model configuration sources, scope, effective time, and decision provenance?
- A plan includes entitlements, users can purchase add-on capacity or receive temporary campaign credits, and contract changes may require manual compensation. How would you distinguish entitlement definitions, granted balances, sources, expiry, and consumption records?
- Business users can edit rules ahead of time, schedule them after approval, and still have older versions referenced by some users and asynchronous jobs. How would you model draft, review, publication, effective time, and rollback?
- A product offers one free trial, but users may register with another email, share a device with family, or qualify through a partner channel. How would you define the eligible party, exception sources, abuse boundaries, and appeals?
- Several teams maintain customer profiles. When data is wrong, no one knows which system is authoritative, and systems also write values back to one another. How would you define field ownership, source of truth, synchronization direction, and dispute handling?
- Business categories may be added, merged, or renamed. Reports must reproduce the definition used at the time and compare results under the current definition. How would you preserve source categories, mapping versions, and report definitions?
- A service requires a user, platform, and partner to act in sequence. Each party measures its own SLA, yet users still wait repeatedly and resubmit information. How would you model the end-to-end journey, waiting ownership, and handoff costs?
- An accountant uses one identity to manage several legal entities, each with separate contracts, invoices, and approvers; some group reports allow cross-entity summaries. How would you model identity, membership, resource ownership, and cross-entity access?
- Plans sold through different channels share a display name but have different features, quotas, and renewal terms; users may switch channels during an upgrade. How would you distinguish the catalog display, sellable offer, contract version, and effective entitlements?
- The team wants to move eligibility checks from service code to a configurable rules engine so Operations can adjust them; many historical exceptions exist and execution order is implicit in code. How would you discover rules, verify semantic equivalence, and govern configuration access?
- A product changes permanently valid credits to monthly refreshes, but some older contracts promise permanent balances and users have accumulated unused credits. How would you version rules, balance lots, contract cutovers, and user explanations?
- A user belongs to several organizations. The browser retains prior-workspace cache, and old organization data briefly appears after switching. How would you design the boundary?
- A contract charges monthly, while the customer accepts work by project. Some months include preparation but no visible deliverable. How would you distinguish signing, performance, acceptance, and recognizable revenue?
- An enterprise plan includes seats, feature modules, and regional restrictions. The customer adds and removes seats mid-term. How would you model the contract, entitlements, usage, and change history?
- A channel brings many low-priced orders but requires extra manual checks and complex delivery. How would you assess whether revenue covers service cost, refunds, and supply risk?
- An account is active weekly and likely to renew, but many tasks rely on manual work by customer success. How would you distinguish product use, service assistance, and sustainable value?
- A service depends on platform capabilities, partner fulfillment, and the customer’s own process. The owner wants to know where failures occur. How would you map the parties, commitments, handoffs, and outcomes?
- A user may try a service, subscribe, pause, and later return. Product, operations, and finance count different events. How would you define lifecycle stages and transition rules?
- A feature serves newcomers, administrators, and expert users, each with different obstacles. How would you separate shared needs from role-specific needs without forcing them into one solution?
- A customer-facing capability spans identity, billing, notifications, and data teams. Each team can explain its local behavior, but no one owns the end-to-end promise. How would you define interfaces, owners, and acceptance boundaries?
- Sales materials combine several features into one offer, while entitlements and service levels live in separate configurations. How would you map the customer promise to verifiable product capabilities?
- A partner replaces manual review with batch processing. Wait time drops, but exceptions appear later. How would you decide whether customer workflows, service promises, and internal operations should change together?
- Three business teams need similar approval capabilities. Some want a shared platform; others fear an abstraction layer will slow delivery. Which user tasks, change patterns, and governance costs would guide the boundary?
- Conversion rose after a product redesign, while the service team also changed its workflow. How would you model the shared outcome without attributing it only to the online funnel?
- A proposal repeatedly refers to “core users” without identification rules, observation windows, or exclusions. What would you clarify so the team can study the same population?
- Administrators want all data on the settings page, while members need only task information. How would you define a common information structure and role-specific presentation?
- Marketing proposes behavior-based discounts that may raise revenue, but customers can compare offers. How would you define pricing rules, disclosure, and risk monitoring?
No questions in this section match your target. ·
2. C · Value judgment and direction setting80
- A marketplace raises commission by two points. Revenue rises short term, but some high-quality suppliers list less often; buyer conversion has not moved yet. How would you assess long-term impact?
- After a subscription price increase, monthly revenue rises 8%, but cancellations grow among small core customers. Sales wants to continue. How would you estimate net benefit and long-term risk?
- Gross margin is steady, but standard-service revenue falls while custom-service revenue grows, along with implementation and support hours. How would you determine whether growth is healthy?
- An acquisition campaign drives many registrations, but some regions cannot yet be served, reducing the share of new users who can actually receive the service. How would you define and report the campaign result?
- Product, operations, and sales reports all say “retention,” but refer to return visits, key-feature use, and renewal. How would you clarify the measures so each name maps to a user behavior and business decision?
- A major customer will pay a high price for a custom feature, but reuse by other customers is uncertain. Ongoing maintenance, permissions, and data rules add cost, and sales has promised a delivery date. How would you compare a one-off build, productizing it, a service, or declining—and decide whether to invest?
- Interviews and support tickets repeatedly mention the same problem, but few users in a pilot are willing to change their current workflow. How would you determine whether the issue is how the need was expressed, switching cost, target-user selection, or problem priority?
- You inherit a mature product with a stable user base and stalled growth, and the team wants to launch new features immediately. What product understanding would you build in the first two weeks before deciding where to invest?
- Next quarter, the team can keep only one initiative that directly drives growth and one foundational capability project, and each option has strong advocates. How would you compare them and choose a portfolio?
- A major competitor makes a feature free that large customers have repeatedly requested, but you have not observed customer losses because of it. How would you determine whether this is an emerging competitive risk, a negotiation signal, or a feature gap not worth following?
- A feature is used often but has not improved retention or payment. How would you determine whether it creates core value, reflects habit, or rewards the wrong behavior?
- For the whole, is the part you own a lever, a fulcrum, or just one link? How do you judge that, and how do you show it is not merely important-looking?
- How would you calculate a product direction’s return on investment? How would you account for labor, cost, and revenue, use annual recurring revenue (ARR), and identify where the calculation might overstate value?
- A competitor launches a lower-priced substitute. Customers start negotiating harder, but usage has not changed much. How would you choose a response?
- A free feature attracts many active users, but inference and support costs rise too. How would you evaluate the business role of the free tier?
- What business result did your project bring? How do you confirm it came from this project and not from something else?
- Who you compare against changes the conclusion directly. Why did you choose these comparisons, and how would your conclusion change with a different one?
- When you benchmark against a competitor's data, how do you decide what is comparable and what is not? What decision did you finally use it for?
- How is your core metric defined? What are the numerator, denominator, time window, de-duplication, and exclusion rules, and why is it the core metric?
- How was your funnel built? Why are the steps divided the way they are, where does most of the drop-off happen, and how do you confirm the steps neither overlap nor leave gaps?
- How do changes at each funnel stage ultimately act on the business metric? Improving which stage by a little moves the business metric the most, and what is that judgment based on?
- Once your metric is converted to the industry's common definition, where does it stand? What assumptions did the conversion make, and what information did it lose?
- A dashboard holds dozens of metrics and the team's attention keeps getting pulled to the most visible numbers. Pick one user task and explain how you would tier the metrics and decide which enter the core list.
- A target was set for a metric you own. How do you break it down into specific levers and actions, and judge along the way whether it can be met?
- The metric was met, but you felt the business did not really get better. Has that happened to you? How did you notice, and what did you do?
- After a feature launches, how do you judge whether it met its original goal? When do you review it, and what would you decide differently afterwards?
- The boss raises a business pain, such as high acquisition cost and poor retention. How do you translate it into goals the technical team can tackle, and show how technical means act on those business metrics?
- For the last new feature you launched, what were the specific before-and-after changes in the core metric, such as conversion, click-through, or retention? If the numbers fall short of expectation, along which dimensions do you usually investigate the cause?
- The target metric improved, but refunds, complaints, or manual handling also worsened. How would you decide whether the outcome is acceptable?
- The initial effect of a feature is strong but fades over several months. How would you distinguish novelty from lasting behavior change?
- Several teams changed the product, pricing, and operations at once, and the overall outcome improved. How would you assess each contribution?
- A pilot meets its target, but results vary when expanded to more regions or segments. How would you judge whether the result is replicable?
- A redesign improves paid conversion but leaves more users unable to complete a core task. How would you judge whether the growth is worth it?
- How do you confirm that your team's goals are consistent with the company's strategic goals? When they are not, do you adjust the team's goals or try to influence the goals above?
- If you had to plan a technical direction over three to five years, how would you do it? How do you keep it from becoming a vision list that cannot be tested?
- The company’s growth is slowing, and your manager asks you to explore an unfamiliar, highly competitive market with a limited budget. What would you learn and test in the first 30 days, and what evidence would determine whether to continue or stop?
- How did you apply the industry's practices to your current business? Which applied directly, which needed adapting, and which did you judge not to apply, and why?
- A high-traffic flow was changed into sequential steps, raising overall completion. Support reports, however, show users struggle to find exit, undo, or change options. How would you determine whether this is a real experience improvement, a segment difference, or a metric artifact?
- Is your approach unique or forward-looking? What did you bet on at the time, was it later proven right, and what would show that you were wrong?
- You say this solution is the most advanced in the industry. What is that based on, and what did you compare against, along which dimensions, and as of when?
- A legacy feature has few users but supports month-end reconciliation, and maintenance cost keeps rising. How would you compare migration, paid maintenance, and retirement?
- Describe a product decision where a short-term metric worsened, but the team expected a longer-term benefit. What evidence informed the decision, how did you monitor it, and what later evidence linked the outcome to that choice rather than outside factors?
- A new process doubles weekly feature releases, but task completion is unchanged and support tickets rise slightly. How would you decide whether to continue, adjust, or stop?
- Describe a technology-platform project you worked on that few teams used and that produced little visible business value after launch. What evidence or assumptions justified the investment at the time? Which assumptions did later evidence disprove, and what validation did you add?
- The request is 'add an Export to Excel button to the order list page.' Show how you move from the surface request to the user's behavioral obstacle, and then to the value outcome.
- A colleague proposes adding a settings switch to a feature. Before discussing how to build it, which questions would you ask to judge whether the switch is worth building?
- Overall onboarding conversion falls. The funnel shows the most exits at address verification, but support records point to identity checks. How would you choose research and fix priorities?
- How does technology truly drive the business, rather than merely support it? Tell me about a time technology opened a possibility the business did not have before, and how you judged it was not just technology amusing itself.
- When you did your research, what were the industry level, the best practice in this direction, and the level already reached inside your company? Where does your solution fall, and why?
- Drawing on available material and direct observation, which kinds of companies do you think this technology will affect most over the next two years? Explain your own judgment and evidence rather than only repeating industry reports. What does it mean for your company, and what have you done to test or respond to it?
- The team wants to 'use our own product more,' but the last experience night produced only scattered impressions. How would you design it so self-use becomes a feedback loop that runs from a real task to a verified fix?
- Brand asks for low-contrast text, but users with low vision struggle to read it; increasing contrast changes the brand presentation. How would you make and validate the design decision?
- A critical flow is two weeks from launch when a review finds that keyboard users cannot complete one step. A full redesign would affect the date. How would you assess the impact, negotiate scope with the team, and explain what can be staged versus what cannot safely ship?
- After a redesign of an important flow, the expected completion rate does not improve. Support requests decline, existing users respond more positively, but new users behave worse. How would you check metric definitions and user segments, determine what effect the design had, and choose the next action?
- A mobile onboarding redesign helps more users complete setup on day one, but active retention drops two weeks later; the flow also requests more permissions. How would you judge whether short-term conversion masks lower long-term value or loss of trust?
- An AI assistant increases apparent task-completion rates, but users recheck every result and some errors cause downstream rework. How would you judge whether automation actually lowers total task cost?
- A new checkout flow omits a fee explanation and increases payment conversion, but refund questions and cancellations also rise. How would you decide whether short-term conversion is worth it and identify evidence that the design created an expectation gap?
- Analytics show target users skipping the product's main flow and using exports, spreadsheets, or manual coordination instead; the team believes this is a user-habit problem. How would you decide whether the product conflicts with real work practices?
- A new operations dashboard is visited often, but interviews show most people only take screenshots before reviews and do not adjust resources or actions. How would you decide whether it creates decision value or only serves a display need?
- A keyboard-navigation defect affects few users but prevents them from completing a critical task; a feature expected to add revenue is also waiting. How would you compare user harm, obligations, opportunity cost, and repair scope?
- A premium feature available only on mobile has few users, but they renew and show strong willingness to pay; continued support increases cross-platform differences and testing cost. How would you decide whether to expand, retain it as a premium capability, or stop investing?
- Growth, Support, and Product each want a new home-page entry; each change helps one group but could make the core task harder for first-time users to find. How would you choose the entry priority and experiment sequence?
- The roadmap lists many goals but no explicit exits; each new request is added on top, and commitments keep changing. How would you include stopped, deferred, and declined work in planning governance?
- The team defines conversion as purchasers divided by visitors. After a redesign, visits fall while purchaser count stays roughly flat, so the rate rises. How would you decide whether the redesign improved the target user's purchase experience?
- A product change increases setup completion, but renewal and long-term use take months to observe; the team wants to invest more based on the proxy. How would you assess its link to final outcomes and the risk of deciding now?
- A redesign raises recommendation scores, but app-store complaints and escalations to support also increase; the sources have different users and response timing. How would you decide whether experience truly improved?
- Support quality was measured by response speed. Automation now shortens first response without reducing resolution time, and complex cases are split into multiple tickets. How would you redefine success and guard against gaming?
- A new product could enter several regions: the largest requires local partners and complex compliance, while a smaller one has existing channels but a narrower segment. How would you compare target-customer demand, local payment and service conditions, entry cost, competition, and learning potential?
- A self-service flow reduces agent volume, but users with complex issues wait longer after escalation and total complaints do not fall. How would you define the end-to-end outcome and identify costs shifted by local optimization?
- The same customer submits changing feature requests, all pointing to delayed month-end reconciliation. How would you uncover the underlying problem and validate priority?
- Three teams propose shared-capability projects, each citing different future benefits with no near-term customer commitment. How would you validate and sequence platform investments?
- A new feature reaches only half its adoption target, but many target users have not received training or access. How would you diagnose and adjust the plan?
- A feature is rarely used, yet enterprise procurement and renewal interviews consistently cite it as a safeguard. How would you assess value and decide investment?
- A configuration form has 28 fields. A multi-step design may increase abandonment, while one page is hard to understand. How would you gather evidence and decide?
- A map relies on dragging and zooming, making the same location data hard to access on mobile and by keyboard. How would you design equivalent controls?
- A key customer wants to skip an approval step to speed up processing, but other roles rely on approval records for audits. How would you assess local efficiency and system risk?
- Sales wants to promise support for an external platform next quarter, but technical validation has not started and the customer planned a migration around it. How would you handle timing and commitment?
- Customers keep asking for options, and support teams use flags as workarounds. How would you distinguish stable needs, temporary exceptions, and a broken product abstraction?
- An onboarding test improves short-term activation, but most participants came during a promotion and long-term retention is immature. How would you judge the evidence and next step?
- High-value customers want more approvals, everyday users want fewer steps, and internal teams want extra checks. How would you return to the shared task and decide what to validate first?
No questions in this section match your target. ·
3. D · Delivery and ongoing operations11
- A new-customer offer generates many registrations, but most users do not complete the first key action and the discount cost has already been incurred. How would you plan follow-up and decide which users merit further investment?
- A channel has a low acquisition cost in a small test, but lead quality and conversion fall as spend increases. How would you validate the cost definition and true incrementality, distinguish channel saturation from audience or sales-capacity changes, and set a limit for additional spend?
- Different teams provide conflicting data and explanations for the same business problem, while the project is already planned for this quarter. How would you decide what to investigate first and what to defer?
- Tell me about the most complex feature you owned. How do you break a vague business request down, step by step, into a requirements document without logical gaps, and how do you design fault tolerance and interaction for edge cases such as a lost connection or an abnormal account?
- A customer asks for “a real-time dashboard,” but their examples suggest they only discover inventory errors later in the day. How would you guide the discussion?
- Engineering tells you that, because of the underlying architecture, the feature you specified will slip two weeks, while the business side wants it tomorrow. How do you cut half the features in a short time and keep a minimum viable version that can ship, and what do you rely on to decide what stays and what goes?
- A request says only “reduce user form time,” without explaining optional fields, consequences of bad data, or workflow differences. How would you decompose research, interaction design, technical validation, and outcome acceptance?
- Operations manually grants replacement benefits to resolve complaints quickly, but weekly compensation volume keeps rising and causes are classified inconsistently. How would you protect users now and turn compensation data into product-fix signals?
- Leadership asks for higher engineering productivity next quarter without defining it. Some propose increasing commits; others want fewer meetings. How would you establish an improvement direction?
- Several product teams aim to reduce complaints, but categories, channels, and ownership differ. How would you define a shared measure and team actions?
- A shared component already has many variants, and a new use case requests another special state. How would you weigh reuse, complexity, accessibility, and maintenance?
No questions in this section match your target. ·