116
edits
12%-time: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
Slack in projects is important. A fully utilized project (or team) is virtually guaranteed to fail to meet its deadlines: any small delay during a project would cause you to violate the deadline. One of the ways we ensure slack is included in our workweek, is by booking ''up to 4 hours'' every week of 12% time. Yes, that's actually 12,5% of your 32-hour workweek, but the shorter name has stuck. | Slack in projects is important. A fully utilized project (or team) is virtually guaranteed to fail to meet its deadlines: any small delay during a project would cause you to violate the deadline. One of the ways we ensure slack is included in our workweek, is by booking ''up to 4 hours'' every week of 12% time. Yes, that's actually 12,5% of your 32-hour workweek, but the shorter name has stuck. | ||
Secondly, 12% time allows for experimentation and learning outside our regular projects. The availability of work shapes projects. It might benefit Delft Solutions to have you know React, but a React-based project might not come up for months. 12% time allows for learning React on your terms. Or we might want a new plugin to calculate vacation hours in Kimai, but can't create a project for that. You could build it in 12% time. 12% time allows for exploration of new ideas, innovation outside of your daily responsibilities, skill development, and potential development of new products or features. | |||
== Doing 12% time at Delft Solutions == | == Doing 12% time at Delft Solutions == | ||
# What to work on: | # What to work on: | ||
## Choose your own topics & projects. Noone assigns you 12% work. While others might have suggestions, you decide how to allocate time. | ## Choose your own topics & projects. Noone assigns you 12% work. While others might have suggestions, you decide how to allocate time. | ||
## You can work on things over multiple weeks, or | ## You can work on things over multiple weeks, or choose a different topic every week for variation. | ||
## What you work on, should be "work-related". We take an expansive view of that requirement; it doesn't have to be directly related to your job. Learning a new programming language, trying some new technology, building a badge reader for the office door, learning bookkeeping or accounting, making a meeting timer, etc. are all great examples of using 12% time. On the contrary, underwater basket weaving, sleeping and remodelling your bathroom are not. | |||
# How to budget time: | # How to budget time: | ||
## Limit your 12% time to 4 hours per week over a long term average. It's okay to spend more or less time on 12% time per week, it doesn't have to be exactly 4 hours. | ## Limit your 12% time to 4 hours per week over a long term average. It's okay to spend more or less time on 12% time per week, it doesn't have to be exactly 4 hours. | ||