Strand builds real-time dependency mapping and change impact tooling for DevOps teams. Their product sits at the intersection of visibility and trust: engineers need to know exactly how their services connect before they ship a change, not after something breaks. The team had spent years refining how they visualized architecture, but the way they managed their own internal work had not kept pace with how fast they were moving.

The problem with task-first thinking.

Before Velocy, Strand ran their planning the way most engineering teams do. They had a backlog, they groomed it weekly, they moved tasks across a board, and they shipped. On the surface it worked. But Jack Peterson, Co-Founder, noticed a pattern that was hard to ignore. "We were finishing tasks and still missing goals," he said. "The work looked busy but the outcomes weren't moving the way they should." Individual tickets were getting closed on time. The goals those tickets were supposed to serve were not.

The issue was not effort. The issue was that task-first tools do not tell you whether the work you are doing is actually connected to the thing you are trying to achieve. A sprint can end green and a goal can still slip. Strand had built a product that solved that exact problem for infrastructure teams, and they were living the same problem in their own sprint planning.

Switching to outcome-first planning.

Strand switched to Velocy at the start of Q2. The adjustment was not immediate. Peterson was candid about the first two weeks: "The instinct is still to jump to tasks. You have to consciously work backwards from the goal and let the structure follow from there." Once the team settled into that habit, the change became obvious in the work itself. Tasks that would have previously made it onto a sprint because they felt relevant started getting filtered out naturally. If a piece of work could not be traced back to an active goal, it did not get scheduled.

That filter alone changed the shape of their planning sessions. Before Velocy, weekly planning at Strand ran between 60 and 90 minutes. Within a month of switching, those sessions were consistently under 20 minutes. The decisions that used to happen in meetings were now made upstream, at the goal level, before anyone opened a task list.

From 11 weeks to 8 days.

The result that stands out most is cycle time. Strand tracked the time it took to close a defined goal from when it was opened to when the last piece of work shipped. In the six months before Velocy, their average was 11 weeks. In the six months after, it was 8 days. Peterson was measured about the reason: "It was not that we started working faster. It was that we stopped working on the wrong things."

Velocy surfaces tasks specifically generated to serve the goal they belong to. Work that does not move the outcome does not appear. For a team like Strand, whose engineers were already working at a high pace, removing that overhead did not change how hard they were working. It changed what that effort was pointed at.

Blockers stopped disappearing.

One thing Strand noticed quickly was how differently blockers behaved inside Velocy compared to their previous tool. In their old setup, a blocked task would sit quietly in the board until someone asked about it in standup or a deadline made it visible. By then, the cost had already accumulated. "You find out about blockers when they've already cost you two or three days," Peterson said. "At that point you're recovering, not planning."

In Velocy, a blocked task surfaces alongside the goal it belongs to and shows the team exactly what it is slowing down. The blocker does not exist in isolation. It exists in context. Strand's engineers started resolving blockers faster not because they were more diligent, but because the tool made the cost of waiting visible in real time rather than revealing it after the fact.

A tool that fits how they think.

Part of what resonated with Strand was how closely Velocy's structure mapped to their own product philosophy. Strand was built on the premise that teams make better decisions when they can see their whole system clearly. Velocity operates on the same idea applied to the work itself. Goals, tasks, and blockers are not separate lists to manage. They are one connected view that shows you exactly where things stand and what is at risk.

"We built Strand because engineers were making decisions without the full picture," Peterson said. "Velocy felt familiar for that reason. The whole point is that you can see what's actually happening, not just what's been reported." For a team that thinks about visibility for a living, that framing was a natural fit.

What changed and what did not.

Strand did not change how many hours they worked. They did not restructure their team or rethink their roadmap. They changed where decisions got made and what information was available when those decisions happened. The goal cycle dropped from 11 weeks to 8 days because more of the work was pointed at outcomes from the start, and less of it was accumulating in a backlog that looked productive but was not moving anything forward.

Peterson put it plainly: "The velocity was always there. We just stopped wasting it."