Browse other categories:
Sometimes you need to bundle tasks together without the overhead of creating a template first. We built ad-hoc processes for exactly this scenario - here is why and how.
Most users complete tasks with a checkmark. Power users discover settings like guest assignment, skip rules, completion windows, and acknowledgement steps that transform how work gets done.
The internal story of building AI template generation at Tallyfy. What works, what fails spectacularly, and why human oversight turns out to be non-negotiable. Real GitHub issues, real performance data.
AI can generate workflow steps, but it misses 50-70% of what makes a process useful. Form fields, automations, and context-specific logic still need human design.
After an attacker sent 10,000+ phishing emails through our system, we rebuilt how we think about API security. The patterns we learned: database-based rate limiting, tenant validation on every request, and why Redis alone is not enough.
How we built dynamic task assignment based on form field values. The Nashville problem, the guest email question, and why Assign and Assign Only became two different operations.
When a large enterprise needed to translate English playbooks to save millions in translation costs, we built Azure Cognitive Services integration. Here is what we learned.
Every workflow tool claims audit trails. The question is whether anyone actually uses them for compliance. Here is what we learned building audit logging that enterprise customers need.
The internal debates at Tallyfy about flowcharts versus simple rules. Why we chose if-this-then-that over traditional process notation, and what Flowtables were supposed to be.
Why the moment between clicking a button and seeing a result matters more than most teams realize. The psychology of pre-click hover effects, post-click feedback, and how tiny interactions shape whether software feels alive or dead.
The internal design debates on showing and hiding workflow steps dynamically. Why step-level rules beat process-level rules, and how to visualize conditionals without becoming a flowchart tool.
Why one prominent Create button matters more than scattered options. How color, placement, and hierarchy drive user behavior and product stickiness.
When customers want their logo and colors everywhere, the engineering challenge is letting them customize without creating unreadable text or broken interfaces.
How we designed deadline rules that dynamically adjust task due dates based on form field values. The engineering story behind calculating deadlines from user-provided dates.
When you change a workflow template, what happens to the 47 processes already running? Most tools force you to choose: freeze your template or risk breaking active work. We built a dual-version system where draft edits never touch the published version that running processes depend on.
What users see when there is nothing to see tells you everything about product philosophy. Empty states are not absence - they are the highest-stakes design moment in any workflow tool.
What happens to work when someone leaves? The actor doing the disabling receives all active tasks. Why completed tasks keep the disabled owner as-is for audit purposes.
Building real-time validation that tells users what is wrong before they hit save. The internal debates on extensibility, custom rules, and why an infinite set of validations forced us to think differently.
When we expanded Sherlock beyond visibility rules, we discovered that mixing rule types creates unpredictable conflicts. The solution was separation - visibility, assignment, deadline, and status rules that execute in parallel.
The surprisingly tricky problem of email identity for external workflow participants. What happens when someone clicks Forgot Guest Link and the system has to figure out if they are a guest, a member, or both across different organizations.
The permission model for letting external participants follow workflow updates without exposing your entire organization. When guests watch a process, they only see updates for tasks they are assigned to - never the hidden steps.
The design philosophy behind letting external people participate in your workflows without creating accounts, passwords, or remembering yet another login. Real debates and sketches from building guest access at Tallyfy.
Kanban boards look beautiful in demos. Three columns, cards moving left to right, visual satisfaction. But when you have 10+ task states, multiple processes running simultaneously, and people need to edit data inline - the card metaphor falls apart. We learned this the hard way.
How we designed single-click process initiation from email. No login wall. The trust model behind public kickoff forms and why anonymous form submissions required rethinking security assumptions.