Should have a standard, minimal deck, that’s adaptable to projects/clients, and well designed. Less is more on the slide.

Typically using Microsoft products these days, so stand up a Teams for the Project with a dedicated OneNote and Folder structure for docs.

Tabs by General (Central hub for important and critical links), and by Topic / Meeting Type.

Header, intro, actions w/ owner and due date, high level notes by topic, section for reference docs and links.

Reusable, nice looking Word docs. Utilize the table for function coloring sections and creating the structure. Use icons and logos to make it look nice.

Header, intro, agenda w/ topic, time, person, bottom section for reference docs and links. (I tend not to care about or capture attendees)

Depends on the project - preferably weekly. If daily is needed, shoot for async check-in’s through something like Teams.

That means decks and docs are shared at creation as WIP with co-workers, not when tidy. Never taken offline.

But I don’t believe all problems are solved in meetings. Real problem solving requires some solo deep thinking time.

Will think out loud on calls and in text. Show thought process and ensure alignment. Spitballing is my middle name.

Directing work, organizing, structuring, and managing things that result in something tangible and creative.

I don’t believe we should always present ourselves as buttoned up and professional. Even to clients.

I learn fast and on the job to get things done. RPA, SQL, PowerBI - all things I had to learn for the first time while delivering quality at the same time.

Currently: Business Strategy Consultant, MBA and soon, PMP