💃 Polish the Notes | Part 2 of 3 | Salesforce Post-Meeting Tasks 🕺

Good morning, Salesforce Nerds! Now that you’ve decompressed from your meeting 😮‍💨 , it’s time to put a bow on it 🎀.

You ran a great meeting, you gathered business requirements, influenced decision making, and received validations from the client and took your notes 💪.

Now you want to make those notes nice and pretty 🤩.

What and Who are these notes for?

How much polish and refinement do the notes need?

When do they have to be completed?

Great questions! Let’s take a look 👀 

Agenda for today includes

• Polish the Notes

• Daily Principle

• All the Memes

Polish the Notes

Today we will discuss-

✅ Who is the audience and what is the purpose of these amazing notes?

✅ How much “polish” 💅 do the notes need?

✅ When do these notes need to be done?

Who Is The Audience And What Is The Purpose?

The audience is the project team, and for 3 purposes-

1. Client/stakeholder decisions.

2. Client/stakeholder validations.

3. Project deliverables documented - exception management, risk callouts, bus reqs, design elements, build details, due dates, etc.

Project team is not to be confused with executives, who have their own documents you’re creating.

The project team needs the ability to reference back to the notes for decisions, validations, and notes on how exceptions will be managed.

Examples of each-

• Decisions- stakeholder confirmed their requirement is MSPL instead of checkbox

• Validations- stakeholder confirmed their requirement is MSPL field instead of a checkbox fields and they understand how this impacts external reporting

• Exceptions- Billy, a Sales user, is the only user who works in multiple regions. He will need exceptional record access which will require manual updates for each region he needs to see.