Design / Create intentional experiences
Once you understand
the cause,
you can change
the system.
Design turns evidence-supported understanding into a practical future state: clearer workflows, communication, ownership, and human interactions.
Redraw the system ↓Evidence gives change a reason
Every change should have a reason.
A solution can sound smart and still solve the wrong problem. Design begins with a supported understanding of the cause, then defines what the system needs to do differently.
Supported cause
Responsibility for post-interview updates is unclear.
Design requirement
Make communication ownership explicit.
Intended experience
Candidates receive clear, consistent updates.
Success question
Did communication consistency improve?
Educational example, assuming the cause has been validated. This shows the connection between evidence and change, not the internal design method.
Current state → intentional state
Redesign does not mean replacement.
Useful parts of a system can stay. The change should address the condition that needs attention.
Interview preparation
Candidates receive helpful information before the conversation.
Post-interview update
The next communication has no clearly accepted owner.
Repeated follow-up
People chase the same unanswered question across handoffs.
Reveal an intentional state
Preparation stays
Retain the information that already helps candidates arrive ready.
Ownership is explicit
Define who sends the update, when it is due, and who covers an absence.
A clear route for questions
Give unresolved questions an owner and an escalation path, reducing repeated chasing where the evidence supports it.
The intended result is a more dependable experience. The result still needs to be tested in practice.
Illustrative architecture—not client evidence or a universal recommendation. Extra approvals, interviews, and handoffs should be removed only when their purpose and consequences have been considered.
Start with the human
What should someone experience here?
Select a topic to explore
Application
Does the candidate understand what happens next?
Preparation
Do the candidate and interviewer have what they need to arrive ready?
Waiting
Can the candidate understand the status and reach someone with a question?
Interview
Does the conversation have a clear purpose and respect the person’s time?
Decision
Is the decision process understandable, with accountable ownership?
Closure
Does the journey end clearly and respectfully, whatever the outcome?
Transparency
Make the experience understandable.
Preparedness
Help people arrive ready.
Respect
Value time and effort.
Care
Recognize the person.
Trust
Make commitments dependable.
Public design questions and experience dimensions—not a scoring rubric.
The support underneath
A process without ownership is a hope.
A clearer message depends on more than its wording. Workflows, decision rights, responsibilities, technology, and governance must support what the candidate is being promised.
Select a topic to explore
Make responsibility clear
Who owns the action? What must happen, and when? What does the candidate need to know? How will the organization know it happened?
Design for change
Documentation, review, and clear decision rights help the experience remain understandable when people, hiring volume, or technology change.
Include the exception
When an interviewer becomes unavailable, a candidate needs help, or a system fails, define how a person takes responsibility and how the next step is communicated.
Consistency with room for context
Standards create the floor.
Humans create the moment.
Too little structure
The experience depends on individual memory and extraordinary effort.
Too much rigidity
A script can become a barrier when someone needs a different kind of help.
Intentional structure
Clear expectations, accountable judgment, and room to respond to the person and situation.
Make it work in reality
Design for the conditions
the team actually has.
Constraints belong in the design.
Capacity, budget, existing systems, organizational responsibilities, legal requirements, and readiness for change affect what can operate sustainably. A future state should work within real constraints and identify what must change to make it viable.
Technology serves the experience.
Define the intended experience and what the system must support before choosing a tool. AI may assist repetitive work and organize information; human review, candidate access to a person, and accountability must be explicit.
Define success while designing
What would better look like?
Every meaningful recommendation needs an intended outcome and a way to assess whether it happened. Clearer ownership, for example, should lead to a testable question about the consistency of candidate updates.
Defining that question is part of Design. A proposed future state is not proof that the experience has improved.
Direction that can be acted on
An intentional target state.
Not a wish list.
Design defines what the system should become and why. Making approved changes operational is a separate responsibility, requiring people, decisions, and follow-through.
The intended architecture can be explained clearly while its detailed engineering specifications remain protected.
When the evidence says something works,
preserving it can be the right decision.
Change should
earn its place too.
Build on purpose.