While it’s a gross oversimplification to say that I draw (I use the term “draw” loosely) on a whiteboard for a living, it’s amazing to reflect on how much of my time is spent using a whiteboard for all kinds of things (most of which are incredibly valuable to the work I’m doing). I can tell I’m spending a majority of my time on the whiteboard while at work, because my smartphone pictures are about 25% whiteboard pictures and 75% pictures of my adorable son (and beautiful wife).
As a Chief Technology Officer, I end up using the whiteboard for all kinds of things, like:
- Facilitating solution architecture discussions and development with subject matter experts (technical experts) and people who understand the needs of our customers, creating things like Concepts of Operation (ConOps), system architectures, and unifying proposal roadmap figures
- Outline and storyboarding proposals before we start digging into these (This is key — just like software engineering, you need a plan/architecture before anyone writes any code)
- Creating product backlogs and release plans, where I sometimes throw in some painter’s tape and sticky notes so I don’t have to keep rewriting the user stories when I move them between releases/sprints
- Creating user interface wireframes (whiteboards are great for this, because they force you to focus on the big picture — just like using a Sharpie to sketch these on paper, instead of a pen)
- Creating process map and flowcharts with process owners, trying to define current and to-be business processes (and sometimes trying to map the value of different steps while refining)
- Sketching out tables to validate content structure before going off to create them in a tool like Microsoft Office or Confluence
That said, I want to be clear that the pictures of my wife and son are much cuter than my whiteboard pictures.