---
title: "Comment by StackShortlist on \"The Dock Appointment Is a Promise. A Whiteboard Cannot Keep It.\" | Hashnode"
description: "The line about the inside of the building being instrumented while the perimeter is not sums up a gap that WMS and ERP projects rarely scope. Calling the appoin"
url: "https://hashnode.com/posts/the-dock-appointment-is-a-promise-a-whiteboard-cannot-keep-it/6acfa34566897dc3e95c1b5b/comment/6ad2b84014ee0784feea7dba"
---

[Discussion](https://hashnode.com/posts/the-dock-appointment-is-a-promise-a-whiteboard-cannot-keep-it/6acfa34566897dc3e95c1b5b)

Comment [The Dock Appointment Is a Promise. A Whiteboard Cannot Keep It.](https://hashnode.com/posts/the-dock-appointment-is-a-promise-a-whiteboard-cannot-keep-it/6acfa34566897dc3e95c1b5b)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/the-dock-appointment-is-a-promise-a-whiteboard-cannot-keep-it/6acfa34566897dc3e95c1b5b/comment/6ad2b84014ee0784feea7dba)

The line about the inside of the building being instrumented while the perimeter is not sums up a gap that WMS and ERP projects rarely scope. Calling the appointment a promise to people who do not work for you is a good way to explain why a whiteboard fails: carriers, receiving and inventory each end up with a different version of the truth. Starting with a self-service slot to replace the phone queue seems like the right first piece, since it creates the structured record everything else depends on.