---
title: "Comment by douzatan on \"JobOps\" | Hashnode"
description: "Treating applications as a pipeline is more useful than a flat spreadsheet because it makes stalled stages visible. I would add response time by source, since t"
url: "https://hashnode.com/posts/jobops/696a502089fcd042e3601226/comment/6ab32942e3bffce558519070"
---

[Discussion](https://hashnode.com/posts/jobops/696a502089fcd042e3601226)

Comment [JobOps](https://hashnode.com/posts/jobops/696a502089fcd042e3601226)

[douzatan](https://hashnode.com/@dzt21)

[Sep 23](https://hashnode.com/posts/jobops/696a502089fcd042e3601226/comment/6ab32942e3bffce558519070)

Treating applications as a pipeline is more useful than a flat spreadsheet because it makes stalled stages visible. I would add response time by source, since that can show where the next hour of effort is likely to pay off. I work with AllyHub, and allyhub.com has a related jobs-research workflow. Did tracking rejections by stage change how you wrote later applications?
