A programming language for people who don't program.
A workflow builder asks non-technical people to write conditional logic. monday's whole answer is one idea: make failure almost impossible.
I rebuilt the flow end to end, an employee-onboarding automation, then marked the decisions I'd defend and the one I'd change. Less "here's how monday works," more "here's how I read someone else's first-use design."
The problem
Branching logic, for someone who's never written an if-statement.
A workflow builder hands triggers, branches, and data-passing to a sales-ops manager or an HR coordinator: the raw material of programming, with none of the training. So the real problem isn't the canvas. It's keeping them from ever building something broken.
What I builtWhen an item is created → If status is Done → create "Start onboarding checklist"Live in monday as a draft. The four moves below are how the product keeps that flow from breaking.
Why it's smart
Four decisions, one idea: don't let the user build something broken.
1It asks "what starts this?" first.You can't add a step until a trigger is set, so nothing is ever built to run on nothing.
2Mistakes show up on the canvas.A missing field turns red on the node itself, so you see what's unfinished without opening anything.
3Each step inherits the last.Add a branch and it draws itself; the board and item carry down, so the steps stay in sync.
4You can't publish a broken one.Publish stays off until every required field is filled.
One idea runs through all four: don't let the user make a mistake in the first place. That's why someone with no technical background can build an automation and trust it.
On the canvas
1 · The trigger comes before any action exists.
2 · A required field, flagged red on the node.
3 · One branch, drawn for you; board and item carried down.
4 · Publish lights up only when the flow is valid.
Show judgment · what I'd change
It makes you name the thing before you can see it.
The very first dialog asks for a workflow name and privacy, before you've built anything. You're naming a thing you can't see yet, and committing to it cold.
I'd let the name come last and default it from the trigger, so the commitment comes after the context, not before it.
Why this one
Teaching a complex model, on first use, with zero training and no room to fail, is exactly the job I lead at ZoomInfo. This isn't a product I admire. It's the discipline I practice, read in someone else's work.