Judimint · Free

Submit the request. Before you build anything.

Every project starts with somebody asking for a deliverable. Judimint is where you take that request apart first: what the evidence actually supports, what you are assuming, and what this work really needs. Your first investigation is free and does not need an account.

Start an investigation See a real one first

Takes about ten minutes. Ends with something you can say out loud in a meeting.

A real investigation, start to finish

Here is what happens to that request.

Ten minutes of structured questions, and the conversation with your stakeholder changes completely. This is the actual shape of a Judimint session, using the dispatch request above.

Separate what you know from what you are assuming.

Judimint asks about the request line by line and sorts every answer into evidence, assumption, or gap. Nothing gets promoted to "cause" without something behind it.

Error rate rose from 2% to 7% since the March route changeEvidence
New hires do not understand the exception processAssumption
Whether experienced staff are making the same errorsUnknown

Test the request against the obvious alternatives.

Before anything gets designed, Judimint walks the causes a course cannot fix: the tool changed, the process is ambiguous, the incentive rewards speed, nobody gets feedback until the monthly report. Each one gets ruled in or out with what you actually know.

Decide what this work needs next.

You leave with a position, not a to-do list: the problem as best understood, what would have to be true for training to be the answer, and the one thing to find out before committing anyone's budget.

What Judimint concluded

Two-thirds of this is a process problem. Do not build the course yet.

The error spike tracks a route change, not a knowledge gap, and the exception path is undocumented anywhere. There is a real performance need underneath it, but a refresher course would have shipped against an assumption nobody had tested. Recommended next step: two days of investigation before any design decision.

Where an investigation can end

Judimint does not have one answer it is trying to reach.

The work decides the route. Sometimes you already know enough to design. Sometimes the thing you need is evidence about something that already shipped. And sometimes the honest answer is that this was never a learning problem.

The outcome nobody else offers

Not a learning problem? Judimint will tell you that too.

Most tools in this space are funnels. Answer the questions, receive the recommendation to use the product. That is not a diagnosis, it is a sales path with a quiz attached, and every practitioner can feel the difference.

Judimint is allowed to conclude that you do not need anything else from us. That is the whole point: it is only useful if you can trust what it says when the answer is inconvenient.

  • "This is a process problem. Training will not fix an undocumented exception path."
  • "You already have enough to recommend an operational change. Go make it."
  • "The tool changed last month. Start with the people who own the tool."
  • "Nothing here needs a Learning Rewired product. Here is how to say that to your stakeholder."

Learning Rewired Intelligence™

The reasoning behind the questions, and the memory between the tools.

Judimint is not improvising. Every question it asks comes from Learning Rewired Intelligence: research, evidence standards, and professional judgement made operational. And because LRI carries the context forward, whatever you do next already knows what this investigation found.

How Learning Rewired Intelligence works →

Is learning the right intervention here?
What evidence supports the request as written?
How would we know whether performance actually changed?
You never explain the project twice.

Execient · Coming soon

The investigation does not stay at your desk.

Most of what settles an open question happens somewhere else: on the floor, in a stakeholder's office, watching someone work. Execient is the mobile side of the same project, so an observation you make on Thursday afternoon lands in the investigation instead of in a notes app.

Mobile first, because the evidence is never at your desk.

9:41

Field capture

Dispatch errors · investigation

Open question

Are experienced staff making the same errors as new hires?

Log an observation

Stakeholder conversation

Evidence still missing

Synced to the project · LRI

Two different kinds of help

Judimint helps you do the work. Pionati helps you get better at it.

They are not tiers of the same thing. One is for the request on your desk this week. The other is for the practitioner you are still becoming.

The work

Judimint

Examine the request, decide what the work needs, and route into investigation, design, or evidence — or out of the ecosystem entirely.

Start an investigation

The practice

Pionati

Bring real work, get substantive feedback, see how other practitioners reason, and strengthen the judgement behind your decisions.

Explore Pionati

You are not required to start here. If you already know what the problem is, go straight to the tool you need. Judimint exists for the far more common case: the request arrived already solved, and it is on you to find out whether that solution is right.

Free · No account needed

Paste the request you were handed.

Copy it in exactly as it arrived, wording and all. The vague ones work best. Judimint will ask you what it needs from there.

Start my investigation

Create a free account afterwards if you want to save it or come back.

About ten minutes No credit card, ever, for this part Ends with a position you can defend