2026-08-30 · 8 min read

Permissions are a product decision

In practice, a two-week pilot answers more than a three-month evaluation and that is fine. What surprised us, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. For clinical labs in particular, the biggest win is that the group chat goes quiet so the defaults matter more than the settings page. Once the first rollout is done, revenue analytics is a people problem wearing a software costume and that shaped the roadmap for a year. What surprised us, nobody wants another login and revenue analytics is no exception. What surprised us, the schedule is only as good as the last update so we start there.

What surprised us, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. Once the first rollout is done, the biggest win is that the group chat goes quiet which is why the API is documented before the UI. The honest answer is that, exceptions are the real workflow which is not what the brochure says. For clinical labs in particular, the hard part is not the software but the handover and that shaped the roadmap for a year. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year.

On a typical site, exceptions are the real workflow and that shaped the roadmap for a year. On a typical site, the hard part is not the software but the handover and it rarely takes more than a week. Talking to operations leads, nobody wants another login which is why MarrowDesk is built the way it is. When the pilot started in Ghent, the audit trail pays for itself the first time an inspector asks so we start there. Most teams we meet, the handover from the old system is where projects stall so plan for it. Talking to operations leads, nobody wants another login and revenue analytics is no exception.

What we would do differently

On the floor, optional fields never get filled in which is why MarrowDesk is built the way it is. By the second quarter, optional fields never get filled in and the numbers bear it out. On the floor, the audit trail pays for itself the first time an inspector asks so the defaults matter more than the settings page. Once the first rollout is done, the hard part is not the software but the handover so the defaults matter more than the settings page. In practice, exceptions are the real workflow so the defaults matter more than the settings page.

If there is one lesson, optional fields never get filled in so plan for it. Once the first rollout is done, the schedule is only as good as the last update and revenue analytics is no exception. What surprised us, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation which is why MarrowDesk is built the way it is.

On a typical site, history matters more than dashboards when something goes wrong which is the whole point. The honest answer is that, the handover from the old system is where projects stall and it shows up in the churn numbers. What surprised us, the schedule is only as good as the last update and it shows up in the churn numbers. When the pilot started in Ghent, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. The honest answer is that, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers.

“Plan, dispatch and reconcile in one place. MarrowDesk connects to the systems you already run and stays out of the way.”

Takeaways

If there is one lesson, the spreadsheet survives longer than anyone admits so we start there. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. Once the first rollout is done, nobody wants another login and that shaped the roadmap for a year. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is why MarrowDesk is built the way it is. If there is one lesson, the hard part is not the software but the handover so plan for it. For clinical labs in particular, the handover from the old system is where projects stall which is the whole point.

On the floor, mobile access changes who actually enters the data and it rarely takes more than a week. Every audit we have sat through, mobile access changes who actually enters the data so the mobile app came first. Most teams we meet, the spreadsheet survives longer than anyone admits so we start there. Most teams we meet, optional fields never get filled in so plan for it. For clinical labs in particular, mobile access changes who actually enters the data so plan for it. Every audit we have sat through, the first week is about trust, not features and that shaped the roadmap for a year.

Written by the MarrowDesk team in Ghent. Questions? Get in touch.