I tend to dedicate my mornings to deep work and take my meetings only in afternoons.
I thus reserve the periods of the day where I'm most focused to move forward with my own work and only exceptionally accept meetings on these slots.
Although I don't have meetings, what's should be important to note before you have a frequent meeting would be asking some questions:
1. What purpose does this meeting serve?
2. What happens if I miss a few meetings? What are the consequences, and how likely are they?
3. If I don't have this meeting, what can I get done?
You'll often notice that you often don't need as many meetings as you think. Checking on progress is important, but you should put trust in your team to produce results.
Also, you can also question how long do the meetings actually need to be. It's more than likely some of the time is eaten up by introductions and niceties or other subjects being covered. So if you could streamline meetings, that would also reduce the time taken.
Meetings are a necessary evil. Itโs easy to feel you havenโt gotten anything done, if you do not categorize meetings as work.
Hereโs a few tips that work well for me:
- Plan your week on Sunday evening (week goals/broad tasks)
- Review meetings: make sure they have an agenda/jot down your talking points/expected outcomes from the convo
- Create a master list of tasks and block time on the calendar
- Review progress EOD and plan the following day
- Review EOW and repeat
Timeblocking helps set expectations from the task/time commitment. Start small, youโll get over time.
Replies
AI Link Manager
AI Link Manager
AI Link Manager
Kryptview
AI Link Manager
Flamme โ The AI Couples App
AI Link Manager
Kryptview
Evoke
AI Link Manager
PHPRunner
AI Link Manager
cmdk
AI Link Manager
AI Link Manager
AI Link Manager
Scalenut
AI Link Manager
Loopin
AI Link Manager