When I receive a new meeting invite before I've even spoken with a colleague, I reach out and ask about the purpose of the meeting so that I have some context.
Once I understand what my colleague wants to discuss, I'll do some work ahead of time so that we can have a meaningful discussion during the meeting.
When I review the invite details and my schedule, I may need to propose a new time and duration for the meeting so that it fits my schedule.
After I send the updated invite, I want to know as soon as it's accepted, so that I know our meeting is confirmed.
On the day of the meeting, I like to get a reminder 30 mins before the meeting time, so that I can quickly prep for a meaningful conversation.
During the meeting, I write down a list of action items for us to follow up on together after the call so that we don't drop the ball on execution.
As we complete our tasks asynchronously, I tag my colleague in comments so that he'll receive updates on the work completed without needing another meeting.
Once we've accomplished everything we originally set out to do, I like to walk my coworker through the work we've accomplished so we identify any loose ends.
Grab this Figma template which over 1,700+ designers are using to add the context of the user's story to designs and flows in Figma.
Share out what you learn from your research and experiments to inspire confident decision making that goes beyond 'hunches'.
We've ironed out the overlap across personas, user stories, and journey maps into a simple, extensible framework.
