Blog

Product notes for technical founders shipping with small teams.

Illustrated team meeting around a table with laptops and charts on the wall, six people collaborating in a modern office

Everyone Says They're Not Blocked. The Project Still Is.

Standups ask if you are blocked. Teams still stall on cross-role edges nobody owns. What dependency visibility means in software teams, and why personal status misses it.

Ravel Team · Jul 26, 2026

Engineer pointing at a sprint board covered in sticky notes, with Backlog, Ready, In Progress, and Done columns visible

Everyone Was Busy. The Critical Path Wasn't Moving.

Standups can sound like progress while the critical path is stuck. Why activity updates and AI status summaries miss the blocking edge on a real software dependency graph.

Ravel Team · Jul 20, 2026

Task detail card with editable title, description, departments, leaders, and dates before plan confirmation

After the Graph Is Built, Someone Still Has to Tell the Team What to Do

A correct dependency graph does not assign itself. Review task details before you confirm the plan, then Ravel emails each department what they own.

Ravel Team · Jul 8, 2026

Ravel timeline comparing AI doc-order inference (OAuth before login form) with the correct schedule (parallel work blocked on a shared API contract)

Why "AI Task Generation" Is Easy, and "AI Dependency Graphs" Are Not

Breaking a spec into tasks is mostly solved. Figuring out what actually blocks what is not, and one wrong edge quietly wrecks a sprint.

Ravel Team · Jul 7, 2026

Linear sequential login timeline versus Ravel timeline with parallel backend and frontend tracks blocked on a shared API contract

We Stopped Using Linear. Here's Why "AI-Assisted" Project Management Isn't Enough.

Splitting one login feature into two tickets is not a minor annoyance. It exposes a list-shaped data model that AI summaries cannot fix.

Ravel Team · Jul 6, 2026