Are you an ‘I’ dotter and a ‘T’ crosser?

Are you an ‘I’ dotter and a ‘T’ crosser?
Do you label your fields with the correct Descriptions?
Do you document and comment your code properly?

/* 𝙲𝚕𝚊𝚜𝚜 𝚞𝚜𝚎𝚍 𝚝𝚘 𝚠𝚘𝚛𝚔𝚊𝚛𝚘𝚞𝚗𝚍 𝚁𝚒𝚌𝚑𝚊𝚛𝚍 𝚋𝚎𝚒𝚗𝚐 𝚊 𝚏***𝚒𝚗𝚐 𝚒𝚍𝚒𝚘𝚝*/

Ok, that’s not cool. 😐

It may provide temporary comic relief during a moment of frustration, but it isn’t a good thing to do.

Communication isn’t just about getting your point across.
It’s about the story that you tell about what you want to say.

I built this because
– my boss told me to.
– I need my paycheck.
– it’s a user story that has my name assigned to it.

I built this because
– it leads to a better user experience
– it allows more accurate reports that helps in decision making
– it makes my user’s lives better

Descriptions and code documentation/comments are just some of ways to ensure communication isn’t an afterthought.

When building systems and software, apart from initial documentation around requirements – ongoing documentation is generally ignored.

– the change that got requested but then got changed again
– how to check for errors when we use this manual way to import the data
– updated user manual that reflects the workaround we decided on

Communication is incredibly important, and plays a key role in ensuring project success.

In my next Consulting Discovery Masterclass (starting 11 June), I cover key topics such as
– Consulting Engagement & Delivery
– Running & Facilitating Effective Workshops
– Requirements Gathering – Process Mapping & Design
– Critical Thinking & The Art of Insightful Questioning
– Documenting Strong Requirements
– Delivering Powerful Presentations

Lessons in mastering the communication process is baked into every part of the course.

My #PeiItForward competition is back on… so if you fancy nabbing a no-charge spot on the course by hitting the trailhead and making the world a better place, why don’t you enter? Deets in the comments below.

In the meantime, make sure you describe everything you create in a #Salesforce project, such as
– documentation
– updates to documentation
– orgs
– fields, objects, flows and automation,
– code
… basically ANYTHING that you create from scratch.

No one can look inside your brain.

To be honest, my brain may be just a tad too dangerous for anyone to look inside 😬

#OnThePeiroll
#DontTouchIt
#LabelYorSh!t

ps Ok I _DO_ know the difference between “your” and “you’re” … I am just too lazy to correct it 😁