Anonymized case · Program design

Progress checks that lead somewhere

A coaching guide and monitoring design linked evidence collection to reflection, adjustment, and shared responsibility.

Documented design work

The starting question

An instructional program needed a clear relationship between its learning goals, coaching sessions, progress checks, and follow-up responsibilities.

What the evidence suggested

A completed form still needs a review process: who looks at it, which question they ask, and what changes at the next session. I made those parts of the design explicit.

The instructional response

  • Developed reusable guidance connecting goal setting, planning, practice, reflection, and gradual learner ownership.
  • Explained how baseline and later checks serve different purposes.
  • Connected patterns in progress information with changes to coaching priorities.
  • Documented workflow requirements for requests, returns, reminders, handoffs, and specialist review.

What the record shows

The documented output is a set of tutor guidance and monitoring requirements that makes the intended evidence-to-action process explicit.

What this does not establish

Design documentation demonstrates the work produced. It does not, by itself, verify full implementation, automated operation, or a measured program effect.

The next useful question

Are the checks being completed and interpreted as intended, and do the resulting decisions improve the usefulness of the support?

About the source: Based on a private tutor administrative guide, documented workflow-design work, and the specialist role guide. Program-specific branding and operational identifiers are omitted.

Start with what is happening

Tell me where
the work gets difficult.

What have you tried? What happened? What needs to change?
Those questions give us a place to begin.

Let’s talk about it