Work

Case studies you can try

Four interactive demonstrations, a before-and-after workflow and the websites I’ve designed and built. Demos use fictional people and data; project credits describe my actual role.

Interactive case studies

Demos built on fictional data

People systems · Interactive

Attendance Points Sandbox

Problem: Attendance policies are hard to explain consistently, and a raw point total hides the “why”.

Approach: Make every rule visible — grace period, rolling window, banked credit — and flag cases for human review instead of deciding outcomes.

Try it: Change the policy settings and watch invented employee ledgers and a simulated manager view update.

Learning design · Interactive

Choose Your Onboarding Path

Problem: A folder of onboarding documents doesn’t tell a new person what to do first, or when they’re done.

Approach: Sequence the first month into five steps, each with a task, time, resource type and a clear “done when”.

Try it: Pick a fictional role and work setting, open each step and track progress.

Small business · Interactive

Small Business Digital Presence Review

Problem: Owners are told to “improve their online presence” without knowing what to fix first.

Approach: Walk through five plain-language areas and rank fixes by gap size and the owner’s priorities.

Try it: Choose a fictional business and its goals, answer five questions and get an illustrative action plan.

Teaching · Interactive

Microlearning Lab

Problem: Long walkthroughs feel complete to the presenter, but learners still can’t do the task alone.

Approach: One objective, one worked example, three varied practice questions with explanatory feedback.

Try it: Take a four-minute lesson on writing a support request someone can act on.

Systems thinking

Workflow: before and improved

A fictional employee support request, mapped two ways. Open any step to see the human need, the process choice and the evidence I would review. This is an illustration of method, not a documented result.

  1. Map the current process as it actually happens.
  2. Identify avoidable loops and unclear ownership.
  3. Prototype the smallest useful change.
  4. Test with the people who use it.
  5. Document it where people will look.
  6. Revisit after real use.

Illustrative demo · fictional employee support request · not a documented employer result

Workflow: Before and Improved

Before

  1. 1 Request sent by email
    Human need
    The employee needs to know someone received the request.
    What happens now
    Requests arrive in several inboxes with no shared record.
    Evidence I would review
    How many requests start in different places; how often people ask "did you get this?"
  2. 2 Owner is unclear
    Human need
    The request needs a person who is responsible for the next step.
    What happens now
    Whoever notices the email picks it up, or no one does.
    Evidence I would review
    Requests that sit untouched; duplicate replies.
  3. 3 Repeat follow-up
    Human need
    The employee wants a status without chasing.
    What happens now
    Status lives in someone's head or a private note.
    Evidence I would review
    Number of follow-up messages per request.
  4. 4 Manual status search
    Human need
    Staff need to find past answers quickly.
    What happens now
    Answers are scattered across threads.
    Evidence I would review
    Time spent searching; questions answered differently each time.

Improved

  1. 1 One intake
    Human need
    A single, obvious place to ask.
    Process choice
    One short form or shared inbox with the few fields the team actually needs.
    Evidence I would review
    Share of requests arriving through intake; missing-information rate.
  2. 2 Ownership rule
    Human need
    Every request has a named owner quickly.
    Process choice
    A simple routing rule by request type, with a backup owner.
    Evidence I would review
    Requests without an owner after one business day.
  3. 3 Visible status
    Human need
    The requester can see progress without asking.
    Process choice
    Plain-language statuses: Received, In progress, Waiting on you, Done.
    Evidence I would review
    Follow-up messages asking for status.
  4. 4 Standard response
    Human need
    Common questions get consistent answers.
    Process choice
    Short reply templates linked to a maintained knowledge article.
    Evidence I would review
    Consistency of answers; article updates made from new questions.
  5. 5 Feedback checkpoint
    Human need
    The process improves over time.
    Process choice
    A one-question check after closing and a monthly review of patterns.
    Evidence I would review
    Themes in feedback; changes made because of it.

Illustrative sequence only — no times, savings or results are claimed. Method: map the current process, identify avoidable loops, prototype, test with users, document, revisit.

Selected projects

Websites I have designed and built

Phelimj.com

My own portfolio: a place to show working demos and honest case studies instead of a list of skills.

My role: Designer and builder

Delivered: Information architecture, visual system, WordPress + Elementor build and four interactive demos

What it enables: Visitors can try the thinking behind the work, not just read about it.

LoriPrigmore.com

A professional portfolio for a finance and operations leader, organized around case studies and working models.

My role: Designer and builder

Delivered: Site structure, visual design, WordPress + Elementor build and interactive finance demos

What it enables: A clear, credible introduction backed by examples a reader can explore.

IFENDT.com

A company website for a nondestructive testing services firm, including recruiting and blog content areas.

My role: Designer and builder

Delivered: Website design and build, page structure and content areas for recruiting and news

What it enables: Customers and candidates can find services, company information and a way to get in touch.

UrbanBakeryOK.com

A small-business website for a local bakery.

My role: Designer and builder

Delivered: Website design and build focused on the basics customers look for first

What it enables: Customers can quickly see what the bakery offers and how to reach it.

EduSooner.com

A training and learning site.

My role: Designer and builder

Delivered: Website design and build

What it enables: A home for learning resources and training information.

Teaching and learning resources

Resources for teachers

My Teachers Pay Teachers store is a real example of independent educational resource creation. Classroom practice — clear objectives, worked examples and practice that checks understanding — informs the way I design adult learning.

Teachers Pay Teachers

Let's make something easier to use.

Want to hear more of the story, talk about a training or implementation role, or get help with a small-business website? I’d be glad to connect.