Whiteboard the Day

TL;DR — I started with one or two meetings and a question: what makes a successful staff business case. I took notes on the whiteboard during each conversation, snapped a picture, erased it, and started over. By morning we had found the team’s critical path. By evening, six meetings later, we had alignment on priority and a plan to attack it. Most refreshing day I have had since we started building Cue.

I did not plan today. I had a couple of meetings on the calendar and a question I wanted to chase — what makes a successful staff business case — and I let the rest of the day fill in as I went. Each meeting I stood at the whiteboard and took notes the way I would on paper, except the board gave me room to draw the connections as people were making them. When the meeting ended I took a picture, erased the board, and started over for the next one. By the morning’s end the photos showed a critical path I had not seen when I sat down. By evening, after six meetings with the people the question kept pointing me toward, we had alignment on priority and a plan to go after it.

Our Day pulled by a thread

Remote work lets you drift. The calendar fills itself with whatever shows up loudest, and the loudest thing is rarely the most important. A status sync gets the slot a hard problem should have had. A recurring meeting outlives the question it was created to answer. You spend a week reacting and then wonder why you feel so far from the team. The drift is quiet, which is what makes it dangerous.

What worked today was not a plan. It was a question. I wanted to know what makes a staff business case land — what separates the proposals that get funded from the ones that get a polite nod. I started with one or two conversations and some research, said what I was thinking, and asked each person who else I should be talking to. Their answers shaped the rest of the day. The whiteboard caught the shape of each conversation as it happened. The picture preserved it. The erase let the next one start clean.

I leaned on the reasoning I built for my MBA capstone — the same chain of analysis I used to defend a strategy under questioning — and pointed it at what my team was telling me they were seeing. They were not telling me in any organized way. Nobody on a team mid-build tells you their observations cleanly. It comes out organically and unevenly, in side comments and Slack threads and the way someone hesitates before answering a question. The capstone reasoning gave me a way to take that mess and ask whether it added up to something coherent. Most of the time, it did. The team sees it before I do. My job today was to listen for the pattern and then say it back.

Networks emerge intentionally

That is also how you fight burnout on a remote team. Not with a wellness email — by sitting with someone, asking what they are seeing, and working a problem next to them until both of you understand it better than you did when you started. I did that several times today. Each time I learned something I would not have learned reading a doc. Each time the person I was working with seemed to relax a little. Their problem was now our problem. That is the part the calendar cannot give you.

We have to be intentional about this or we will drift. Remote work does not produce connection on its own. It produces availability. Connection happens when somebody walks into a meeting with a real question and is willing to write down what comes back. The teams that thrive remotely are the ones where somebody is asking and somebody else is answering and both of them know which question is on the board today. That is the discipline. The whiteboard is just where it shows up.

A day that starts with a question and ends with a plan does something a calendar full of status syncs cannot. It surfaces the constraint. It pulls the right people into the room without anyone having to play scheduler. By the time the last meeting wrapped, the team had named the critical path together and agreed on what to attack first. I want more days like that. I think the team does too.