Member-only story
How to bridge the gap between maker’s and manager’s schedule in four steps
If you are a developer, chances are that you see meetings as a necessary evil. Your daily tasks are generally about writing code, or participating in peer-to-peer discussions that result in you writing code. And that’s what you like to do.
When you start working on something more serious, you typically need at least half an hour to dig into the problem, and even more to get in the zone. And it’s not unusual that you need several days to get done with a task.
This way of working is called the Maker’s Schedule, and the smallest block of time is half a day. In your world, an empty calendar equals the chance of really getting things done.
Your manager, on the other hand, operates on a different schedule. Most managers’ days are comprised of formal and informal meetings; talking to customers, analysts, sales, developers and other stakeholders. In fact, a significant portion of their unofficial work description is about leading and attending meetings. This holds true whether they are in a traditional management position or a more informal one, such as product owners, project managers and the like.
These people operate on what is known as the Manager’s Schedule, where a typical time slot is 30 or 60 minutes.
