Deprecated: Creation of dynamic property wpdb::$categories is deprecated in /home/pusbairt/public_html/wp-includes/wp-db.php on line 760

Deprecated: Creation of dynamic property wpdb::$post2cat is deprecated in /home/pusbairt/public_html/wp-includes/wp-db.php on line 760

Deprecated: Creation of dynamic property wpdb::$link2cat is deprecated in /home/pusbairt/public_html/wp-includes/wp-db.php on line 760

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/pusbairt/public_html/wp-includes/comment-template.php on line 1745

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 396

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 388

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 382

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 400

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /home/pusbairt/public_html/wp-content/plugins/contact-form-7/includes/mail.php on line 221

Deprecated: Return type of WPCF7_Validation::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-content/plugins/contact-form-7/includes/validation.php on line 78

Deprecated: Return type of WPCF7_Validation::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-content/plugins/contact-form-7/includes/validation.php on line 72

Deprecated: Return type of WPCF7_Validation::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-content/plugins/contact-form-7/includes/validation.php on line 59

Deprecated: Return type of WPCF7_Validation::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-content/plugins/contact-form-7/includes/validation.php on line 82

Deprecated: Creation of dynamic property WP_Block_Type::$skip_inner_blocks is deprecated in /home/pusbairt/public_html/wp-includes/class-wp-block-type.php on line 357

Deprecated: Calling get_class() without arguments is deprecated in /home/pusbairt/public_html/wp-includes/class-wp-http.php on line 328

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/pusbairt/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Deprecated: Creation of dynamic property WP_Term::$object_id is deprecated in /home/pusbairt/public_html/wp-includes/class-wp-term.php on line 198

Deprecated: Creation of dynamic property WP_Term::$object_id is deprecated in /home/pusbairt/public_html/wp-includes/class-wp-term.php on line 198

Deprecated: Creation of dynamic property WP_Term::$object_id is deprecated in /home/pusbairt/public_html/wp-includes/class-wp-term.php on line 198

Deprecated: Creation of dynamic property WP_Term::$object_id is deprecated in /home/pusbairt/public_html/wp-includes/class-wp-term.php on line 198

Deprecated: Creation of dynamic property WP_Term::$object_id is deprecated in /home/pusbairt/public_html/wp-includes/class-wp-term.php on line 198

Deprecated: Creation of dynamic property WP_Term::$object_id is deprecated in /home/pusbairt/public_html/wp-includes/class-wp-term.php on line 198

Deprecated: Creation of dynamic property WP_Term::$object_id is deprecated in /home/pusbairt/public_html/wp-includes/class-wp-term.php on line 198
Manage Your Energy, Not Your Time – Page 6 – AMBER DAVIS

Manage Your Energy, Not Your Time

Manage Your Energy, Not Your Time

By |2025-07-17T13:30:28+00:00July 17th, 2025|
Deprecated: Creation of dynamic property WP_Term::$cat_ID is deprecated in /home/pusbairt/public_html/wp-includes/category.php on line 378

Deprecated: Creation of dynamic property WP_Term::$category_count is deprecated in /home/pusbairt/public_html/wp-includes/category.php on line 379

Deprecated: Creation of dynamic property WP_Term::$category_description is deprecated in /home/pusbairt/public_html/wp-includes/category.php on line 380

Deprecated: Creation of dynamic property WP_Term::$cat_name is deprecated in /home/pusbairt/public_html/wp-includes/category.php on line 381

Deprecated: Creation of dynamic property WP_Term::$category_nicename is deprecated in /home/pusbairt/public_html/wp-includes/category.php on line 382

Deprecated: Creation of dynamic property WP_Term::$category_parent is deprecated in /home/pusbairt/public_html/wp-includes/category.php on line 383
Uncategorized|0 Comments

Tell me: how do you structure your PhD workday?

Are you following a general 9-5 schedule, assuming you’ll finish your work during those hours (and if not, you’ll squeeze in a little or a lot of extra time in the evenings or on the weekends)?

How do you know you are making progress? Do you use word count or other metrics to keep track?

I have come to realise that academic productivity is — and always will be — non-linear. In the face of this inconvenient truth, we adopt all sorts of systems and conventions in an attempt to keep a sense of control over how our work is going.

– Time-based systems such as an 8-hour workday.
– Output-based systems such as word count.
– Peer-based systems as in: “what is everyone else doing??”
– Effort-based systems when our hours or word count, or whatever our system is, fails to reassure us – at which point we start moving on to thinking we should be doing more, especially when it looks like nothing much is happening on the page.

Maybe if we just keep at it until we absolutely can’t do any more, we will have done enough. But will it be enough?? Feels like it is never enough.

One idea changed the way I think about how to best manage PhD work (and the question of ‘doing enough’): manage your energy, not your time.

It is about understanding your own rhythms, your own creativity — and letting those guide your work. Being aware of your energy levels is essential in making this work.

In practical language: most of us have a few hours each day when we are mentally sharp and we have most mental energy.

Use these hours for your most challenging academic tasks, like writing, every day.
Prioritise this work above all else.

That’s it. That’s the idea.

The rest of the day can be filled with meetings and other tasks, but your most important work gets done. Every single workday.

Now, there is a lot more to this as in life tends to be complicated, but simply reflecting on how this approach compares to how you manage your time and energy now is a good place to start.

Maybe you’ll notice a pattern of working lots of hours without feeling you are getting much done at all.

Or perhaps there are so many distractions you feel you never quite get round to uninterrupted work for a few hours.

Perhaps both.

What do you notice? And does the idea of managing your energy — rather than your time — appeal?

If you’d like support, I am available for mentoring and I would be delighted to work with you. Or, check out my online course — it guides you through designing and implementing what a highly effective work routine, which can help you finish your PhD in just 2-3 hours a day. 

If you found this post helpful, share it? I appreciate it!

Go to Top