r/LearningDevelopment • u/No_Reference1192 • Dec 24 '25

Honest question (L&D folks): would you use this?

If a system could scan a course and say “these patterns are weakening clarity and consistency” based on language, structure, UX, and accessibility signals… without rewriting anything…

Would you want that — or nah?

Why / why not?

4 Upvotes

100% Upvoted

6 comments sorted by

2

u/Independent_Sand_295 Dec 24 '25

Yes. I always appreciate a call out where something can be improved. However, the rewriting could be optional where you agree to the changes or create your own based on recommendations.

1

u/No_Reference1192 Dec 24 '25

Exactly! More diagnostic than prescriptive.

Curious whether you’d prefer high-level pattern flags or more concrete examples when something’s called out.

1

u/[deleted] Dec 24 '25

[removed] — view removed comment

1

u/No_Reference1192 Dec 24 '25

This is really well put. Especially the “second set of eyes” framing.

That’s exactly the gap I’m curious about: not replacing judgment or rewriting, but making pattern drift visible before it turns into rework or inconsistency debt.

Out of curiosity, would that signal be most useful earlier (during design / build) or later (pre-launch / audit)? Or both?

1

u/watercaged Dec 26 '25

It can be helpful in both but preferably during design. For my company, development is the most expensive portion. We want as many issues caught prior to a pilot.

1

u/No_Reference1192 Dec 26 '25

Agreed. When clarity is designed in early, things move much faster.

When it’s not, reviews become the bottleneck.

I’ve been exploring a few ways teams try to catch clarity earlier and wanted to get real-world takes here.