Guides
34 guides on workflow. Practical writing from the team building Atlas, useful whether or not you buy anything.
Work that stays inside one team is easy to keep on track. Work that crosses teams is where it gets dropped, because the handoff depends on someone remembering. Automation is how you stop depending on memory.
A team drowning in half-finished work does not have a motivation problem. It has a starting problem: everyone keeps starting new things because starting feels like progress, while nothing actually finishes.
Work that bounces back (reopened tickets, rejected pull requests, "this is not actually done") is almost always a symptom of a definition of done that lives in people's heads instead of on the page.
Most forms end where they should begin. A submission lands in an inbox, someone re-types it into a tracker, and the intake becomes a manual relay. The point of a form is to skip that relay entirely.
Automation software promises to remove manual work, and it can. But an automation you cannot see when it breaks quietly creates a new kind of work: debugging invisible failures.
Removing a password from a PDF is straightforward and entirely legitimate when it is your file and you know the password. What it is not is a way around protection you were never given.
Page numbers seem trivial until a fifty-page document has none and a reader cannot cite a page. Adding them well is about placement and consistency, not just a running count.
Flattening turns a PDF's interactive and layered elements into part of the fixed page. It is the step that makes a filled form final and a marked-up document safe to send.
Filling a PDF form is easy when it has real fields and fiddly when it does not. Knowing which kind you have tells you exactly how to approach it.
PDFs were designed to be final, not editable, which is why editing text in one ranges from trivial to nearly impossible depending on how the file was created.
Extracting pages is the polite alternative to splitting: you take a copy of the pages you want into a new file and leave the source document untouched.
Reordering pages is best done visually, by dragging thumbnails into place, because sequence is something you confirm by eye far more reliably than by juggling page numbers in your head.
Deleting pages is one of the most common PDF tasks and one of the easiest to get slightly wrong, usually by removing the wrong page or leaving references to it behind.
A page that appears sideways is a common frustration, and the fix is easy, but there is one subtlety that trips people up: making the rotation stick when the file is reopened.
Splitting a PDF is the mirror image of merging, and the same principle applies: the mechanics are trivial, but a little planning turns a crude cut into clean, well-named, self-contained files.
Merging PDFs is simple to do and easy to do badly. The difference between a professional combined file and a messy one is a handful of decisions made before you click combine.
The best way to understand automation is to see real recipes. Here are proven patterns teams use, with the trigger, the action, and the reason each earns its keep.
Splitting a PDF is not one task: it is several, depending on whether you want one page, one chapter, or dozens of individual files. Pick the right method and you save yourself a mess.
Merging PDFs is easy to do badly. Getting a combined file that is ordered correctly, reasonably sized, and easy to navigate takes a little discipline.
A kanban board is not just a to-do list with columns. It is a system for making work visible and limiting how much you juggle at once.
A task system does not fail because the tool is wrong. It fails because it asks for more discipline than a busy week can supply.
Confluence is where many engineering and product teams document, and diagrams are central to that. This guide covers the practical ways to add diagrams that stay accurate as systems change.
Notion is where many teams keep their knowledge, but it has no real diagram editor. This guide covers the practical ways to get good, maintainable diagrams onto a Notion page.
You cannot improve a process you cannot see. Business process mapping makes the invisible visible (the steps, the handoffs, and the places where work stalls) so you can fix what actually matters.
Version history is the safety net that lets you edit a diagram boldly. Every change is recorded, meaningful milestones can be named, and any past state can be restored: so nothing is ever truly lost.
Should you write diagrams as text or draw them in a visual editor? Each approach wins in different situations. This guide lays out the trade-offs and shows how to get the best of both.
An activity diagram is UML's flowchart: a way to model a workflow with branches, loops, and parallel paths. PlantUML's modern syntax makes writing one surprisingly readable.
Mermaid's kanban diagram renders a board (columns and cards) from indented text, giving you a versionable snapshot of work that lives right in your docs.
BPMN is a standard visual language for business processes, precise enough for analysts and readable enough for everyone else. This guide gets you from zero to modeling a real process correctly.
Activity diagrams model workflows and business processes with the rigor of UML. This guide covers actions, decisions, concurrency with forks and joins, and swimlanes for responsibility.
Your operations team is probably doing by hand a dozen things a rule could do for free. Here is the first dozen, ranked by how much sanity they buy back.
The deal does not die in the pitch. It dies in the gaps between the proposal, the contract, the signature, and the kickoff.
Approval workflows exist to manage risk. Most of them end up manufacturing a different risk: losing the deal while everyone waits.
Sending a contract for signature is not hard, but small mistakes cost days. Here is the exact sequence I use.
Ready when you are
Atlas brings tasks, projects, CRM, contracts, e-signature, PDF tools, and analytics into one workspace. Start free.