Skip to main content
Limited Release. The EDK is currently in limited release and is not available to all customers. Commands, generated file layouts, and package APIs may change before general availability. Confirm you’re on the latest EDK version before starting new projects.
Design validation confirms that the proposed Elementum solution reflects the real process before a delivery team begins implementation. Walk through the design with process owners, subject-matter experts, and representative users. This review validates the design brief, not a deployed solution. It should expose missing decisions, unclear ownership, unsupported assumptions, and exception paths while they are still inexpensive to change.

​
Prepare the Review

Bring these materials into the session:
  • The business outcome and process boundaries.
  • The persona and stage matrix.
  • Record-experience and list-view recommendations.
  • Known policies, access rules, service levels, and reporting needs.
  • Representative examples, documents, screenshots, or current pain points.
  • Assumptions, open questions, and capabilities that still need confirmation.
Include people who perform the work, not only the people who sponsor or manage it.

​
Walk Through Real Scenarios

Use realistic examples to tell the story from intake through each outcome:
  1. Typical path: Ordinary work moves through the expected stages.
  2. Incomplete path: Required information or evidence is missing.
  3. High-risk path: Urgent or exceptional facts change the decision.
  4. Return path: Work is rejected, corrected, and resubmitted.
  5. Ownership path: Work is reassigned, escalated, or handed to another team.
  6. Terminal paths: Completed, rejected, cancelled, and other final outcomes remain distinct.
At each stage, ask the responsible person to explain what they would notice, decide, update, and do next. If the design brief cannot answer those questions, record the gap.

​
Review Each Persona

Confirm that every persona can:
  • Recognize the record and understand why it needs attention.
  • Find the information needed for the current decision.
  • Distinguish required work from supporting evidence and history.
  • Identify the primary action and understand its consequence.
  • Find and prioritize work across multiple records.
  • Complete handoffs without relying on knowledge outside the process.
Check that sensitive information, edit rights, approvals, and separation of duties match the intended governance model.

​
Check Completeness and Feasibility

Review the design for:
  • Clear process boundaries, ownership, entry conditions, and final outcomes.
  • Defined failure, return, escalation, cancellation, and reassignment paths.
  • Information with a known source, owner, purpose, and retention need.
  • Actions with explicit outcomes and required confirmation.
  • Reporting, service-level, notification, and Automation requirements.
  • Usability expectations for long, sparse, exceptional, and high-volume work.
  • Accessibility requirements and expectations across devices and screen sizes.
  • Platform assumptions marked as confirmed, needs confirmation, or out of scope.
A coding agent can help compare the brief with known Elementum capabilities, but it should not invent platform behavior. Route uncertain capabilities to the delivery team for confirmation.

​
Record Decisions

Update the brief with:
  • Decisions made during the review.
  • Requirements that changed and why.
  • Open questions, owners, and due dates.
  • Platform capabilities that require a prototype or technical check.
  • Deferred ideas and explicit out-of-scope items.
  • Approval from the process owner and affected personas.
The design is ready for handoff when the key scenarios are coherent, each persona’s job is clear, exceptions have owners, and unresolved assumptions are visible. Return to Record Experiences to revise the brief. After implementation, use Acceptance Testing to verify the working solution against these scenarios.