Solutions Consulting & Implementation

Translating school workflows into technology solutions.

Former educator helping education technology companies understand school workflows, drive adoption, and translate real classroom needs into product solutions.

I help education technology companies turn complex platforms into smooth experiences for schools. Nine years inside classrooms and school leadership taught me where systems break. I now bring that rigour to discovery, onboarding, and enablement in educational technology.

THE GAP I BRIDGE

Nine years inside classrooms and school leadership. The past year building products, reviewing platforms, and consulting for EdTech startups. I sit between a product team and a school and translate in both directions.

What I Do

Needs Analysis Implementation Design Client Onboarding Workflow Mapping

Experienced across school operational systems including assessment, reporting, curriculum mapping, and parent communication platforms.

Justine Shields

Portfolio

Selected Work

Approach

How I Work

Every system I've worked in, from classrooms to startups, has the same failure pattern: tools get built for how things should work, not how they actually work. My approach starts with understanding the gap between the two.

👂

Listen before solving.

I start by understanding the environment, not just the brief. Who uses the system? What pressures are they under? What workarounds have they already built? The workarounds tell you more than the requirements document.

🔍

Diagnose the real problem.

The stated problem is rarely the actual problem. A dashboard that "needs better UX" might actually have a signal hierarchy issue. A tool with low adoption might not have a training problem but a trust problem. I look for the root cause before recommending anything.

Design for the person with the least time.

Nine years in education taught me that if a tool doesn't work for the busiest, most time-pressured person in the room, it doesn't work. I design solutions around real constraints, not ideal conditions.

🔀

Recommend options, not ultimatums.

I present multiple paths forward with clear trade-offs so the team can make an informed decision. My job is to make the decision easier, not to make it for them.

Writing

Selected Articles

EdTech article

EdTech · Product Strategy

Most EdTech dies on first contact with a real classroom

A look at why education technology fails when it meets real school environments, and what it takes to build tools teachers will actually choose to use.

Read article
Article
EdTech · Product Strategy

Most EdTech dies on first contact with a real classroom

A playbook for product teams building tools that survive

EdTech article hero

This is written for designers, product managers, and EdTech founders building products for schools.

Most educational software fails within 30 seconds.

Not because it lacks features. Not because teachers "resist change."

It fails because it is designed for a version of work that does not exist.

Uninterrupted focus.

Predictable schedules.

Spare time to learn new systems.

That is not the environment your product is entering.

Failure on first contact is quiet

When a tool fails on first contact, the damage isn't loud.

There are no formal complaints. No dramatic rejection.

Instead, it quietly kills adoption, retention, renewals, and word of mouth.

By the time analytics report "one-week abandonment," the decision has already been made.

How adoption decisions are actually made

Across nearly a decade teaching in schools in Australia and overseas, I saw the same pattern repeat.

Teachers decide whether a tool fits their day almost instantly.

Not after onboarding. Not after a pilot. Not after training.

The decision happens in the flow of a real day: mid-lesson, mid-incident, mid-interruption.

This is the moment your product must survive.

The operating conditions your product is entering

This pattern shows up anywhere people work under pressure. Classrooms are an extreme case.

Sustained cognitive overload. If a tool isn't immediately obvious, it disappears into the noise of the day.

"Just another thing" is a fast filter. New platforms usually mean extra admin layered onto an already impossible workload. If a product smells like more work, it starts from a position of distrust.

Attention exists in fragments. Time arrives in one- and two-minute windows. Bells ring. Students interrupt. Behaviour incidents happen.

If it takes more than a couple of clicks to reach the screen a teacher needs, the tool will not survive a real timetable.

This isn't laziness. It's triage.

Most tools are mandated, not chosen. Compliance can look like adoption until it doesn't. Real adoption is when teachers would miss the tool if it disappeared.

The Teacher-Time Test (a design gate)

Before you ship anything teacher-facing, run this test.

Fail several of these and the product will be rejected, usually in seconds.

30-second clarity Is the purpose and next step obvious immediately?
1–2-minute completion Can the main action be done between interruptions?
Easy reach Is the key screen within a couple of clicks from where teachers actually live?
Chosen under pressure Would teachers still choose this if it weren't mandated?
Visible progress Does it clearly show "I got something done"?
Gentle on confidence Does it reassure rather than intimidate?
Cognitive offload Does it take things out of teachers' heads?
Staffroom language Does it sound like how teachers actually talk?

This is not a usability checklist. It is a kill-switch.

Why this matters for EdTech teams

Designing for teacher time is not kindness. It is strategy.

Tools that feel lighter spread faster. Renewals are easier when teachers would genuinely miss the product. Support costs drop when workflows make sense. Word of mouth happens when teachers feel respected and understood.

Most school software is tolerated, not relied on.

The tools that survive are the ones teachers depend on under pressure.

The fastest-growing EdTech products do not demand attention. They earn it.

From tools to stewardship

Teachers do not need more platforms. They need systems that close loops, reduce cognitive load, and survive real school days.

I design education products by treating time, attention, and duty of care as the hardest constraints in the room.

When those constraints are central, products survive first contact. When they are ignored, even the most polished roadmap struggles.

If you are building for schools and want your product to survive contact with reality, this is the work.

End of article

Get in Touch

Start a Conversation

If you're hiring for solutions consulting, implementation, or school-facing advisory roles, I'd welcome a conversation.

Connect on LinkedIn