Needs and features
Start with interview evidence. Select what belongs now, later, not at all or still needs validation.
HVE Squad / Power Platform client design
Decide what is needed.
Explain the features and data.
Use HVE to understand client needs, choose technology-specific features and compare the schemas that support them. Leave with a justified first-release design, not a code patch or a predetermined blueprint.
10Client decision scenarios
50Main HVE requests
1Need-to-feature-to-data method
Before implementation
Capabilities are choices, not a checklist.
Should an inspection app capture photos offline? Must checklists be versioned? Does a supplier contact represent more than one legal entity? HVE helps you evaluate the need and the data consequences.
Schema alternatives
Explain the entities, fields, relationships, history and access that selected features need. Compare a smaller model.
Scope and rationale
Apply a changed requirement, walk sample records and give the next person a decision pack they can explain.
Technology-specific, not code-centric.
Canvas mobile/offline, model-driven casework, flow routing, agent knowledge/actions, Pages self-service, custom workbench interaction and BI grain/lineage shape different decisions. Coding capability is not the objective of these exercises.
Canvas mobile/offline, model-driven casework, flow routing, agent knowledge/actions, Pages self-service, custom workbench interaction and BI grain/lineage shape different decisions. Coding capability is not the objective of these exercises.
Live HVE uses the connected Cowork project and actual returned artifacts. Supplied client interviews/design-review findings are fictional; no app implementation or runtime success is implied.
Choose the Power Platform decision context
Which features? Which schema? Why?
Each guide provides client evidence, capability options, five HVE requests, schema alternatives, a changed need and a first-release decision-pack task. No required table/control blueprint is supplied.
10 exercises
No exercises match. Clear the search or choose another mode.
Choose the CoE's minimum capability
Decide central/team responsibilities and first-service features. Distinguish use cases, decisions, service activity and reusable assets in the model.
Decide the CoE scope and dataChoose the order-review service
Evaluate extraction, correction, clarification and review features. Compare source/order/line/issue/history models as needs change.
Decide order features and schemaChoose insight before automation
Compare rota, reminder and deeper analysis. Decide what event, pending-work, follow-up and experiment data the first service needs.
Decide the process-service modelChoose inspection features and data
Assess offline, photos, checklist versions and remediation. Derive visit/finding/evidence/history relationships instead of copying a ready schema.
Decide the canvas-app designChoose supplier self-service features
Decide submission, correction, status and private review. Compare supplier/contact/application/revision relationships and visibility.
Decide supplier features and schemaChoose what the agent knows and does
Scope knowledge, preparation, confirmation, submission and status. Separate transient conversation from persistent business request data.
Decide agent features and dataChoose a safe managed handoff
Decide queue, reconciliation, history and ownership features. Model job intent, attempts, observations and accountable resolution.
Decide the operating data modelChoose a proportionate workbench
Assess custom interaction, availability explanation and accountability. Decide skill/assignment/history relationships without defaulting to an oversized scheduler.
Decide dispatch features and schemaChoose explainable commercial insight
Decide diagnostic versus managed casework. Separate source facts, derived measures, investigation history and actual recovery evidence.
Decide insight features and dataChoose reusable versus client-specific
Evaluate required region, reviewers and client variation. Compare simple attributes, managed references and proportionate common schema.
Decide the client variationLabels describe the decision context, not a mandatory architecture. Actual capabilities/entitlements need verification. Timings and live HVE require a representative rehearsal.
Reusable design decisions
Take the reasoning into client work.
Canvas reference case
From interview to offline/photo/checklist choices, then a model that explains zero/many findings and changing requirements.
Review the canvas decision exerciseFeatures before data
Use cases 01, 02 and 06 to choose a bounded capability set and justify persistent data.
Choose a decision problemVariation and reuse
Use cases 05 and 10 to distinguish standard capability, client rules and schema variation without copying customer identity.
Review client variationEvidence and decision outputs.
The result is a first-release feature/schema decision pack, with reasons and open questions. Earlier maker references are downstream examples, not prescribed schemas or core coding/debugging tasks.