Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
(00:05):
This is Elevated the SnackableWeekly podcast, helping kitchen
and bath designers build abetter business.
I'm your host Brandy Lawson, andin this episode we're playing a
little game of.
Six degrees of software impactbecause let me tell you that CRM
you're considering, it affectsway more people than you might
think.
You know how changing one thingin a kitchen design kind of
(00:25):
creates a domino effect, movethe sink, and suddenly you're
rethinking the dishwasherlocation, the prep space, the
traffic.
Well, the software decisionswork the very same way.
Let me tell you about Alex'sfirm.
She came to me thinking she justneeded to switch CRMs because
leads were falling through thecracks.
Simple enough, right?
But when we mapped out who wasactually being impacted by their
current system, there were somesurprises to say the least.
(00:49):
Grab your worksheet, fireeffects.com/choose if you
haven't already, and let'screate your stakeholder impact
map.
We're going to use Alex's storyas our example because it's a
really good illustration of howdeep this rabbit hole can go.
First up, the obvious players.
Alex started by listing herimmediate team designers losing
track of follow-ups.
(01:09):
Admin staff manually enteringthe same info multiple times,
and the team playing emaildetective to piece together to
conversations.
But here's where it gets better.
What about everyone else?
Let's follow the ripple effect.
So next on to the Direct Impactclub.
First, clients trying to signcontracts and getting frustrated
with clunky systems.
(01:29):
Also vendors.
Waiting for specifications thatare buried in someone's email.
Then contractors showing up tojob sites with outdated
information.
And finally, strategic partnerslike architects and builders
trying to coordinate timelines.
So that's the direct.
Now let's talk about theindirect impact squad.
This is the group of playersthat I think is most often
(01:50):
overlooked, those affected byyour software choices without
even knowing it.
So clients.
Might be wondering why theirdesigner seems distracted.
Spoiler, they're mentallytracking 15 different things
because their software doesn'tnext.
Interior designers you partnerwith, but they're getting
incomplete information.
Also, thinking about installersdealing with last minute changes
(02:12):
or missing pieces becausecommunication fell through the
cracks.
Here's what blew Alex's mindwhen we mapped out everyone
impacted by her small CRMproblem.
Four designers were spendingfive extra hours per week
hunting for information.
Two admin staff, basicallyplaying full-time detective.
15 active clients dealing withdelayed responses.
(02:32):
Eight strategic partners gettingfragmented communications and
three vendors receivingduplicate and sometimes
conflicting orders.
And finally, countless potentialclients who never heard back
from you because they got lost.
But wait, here's the realkicker.
Remember those indirect effects?
Alex had a designer almost quitbecause she was so stressed out
(02:52):
about missing follow ups.
The designer wasn't mad at thecrm, she was mad at herself.
The classic case of good peoplebeing failed by bad systems.
So let's talk about your clientsfor a minute.
You ever have to say, oh, I'llhave to look that up and get
back to you during a clientmeeting.
That's a software impact moment.
Every time your systems make youlook less professional or
prepared, they're affecting yourclient relationships.
(03:14):
So here's how to map your ownstakeholder impact.
First, start with your innercircle list everyone who
directly uses a software.
Then think about what are theytrying to accomplish, and then
how are they currentlystruggling.
Second, follow the informationflow.
So who receives information fromyour system?
Then who needs to inputinformation?
(03:36):
And then where are thecommunication breakpoints?
Number three, look for thehidden impacts.
Who's affected by delays here?
Then where is the frustrationshowing up?
And finally, what relationshipsare being strained.
Remember those, uh, I'll getback to you in moments.
Track those for week.
Each one is a clue about who'sbeing impacted by your current
(03:58):
setup.
Okay, here's the big revelation.
What finally happened with Alex,once we mapped out everyone
affected by their CRM issues,that$12,000 annual software
investment suddenly looked likea bargain compared to 520 hours
of wasted team time annually.
Three missed partneropportunities, one almost lost
designer, and countless stressand headaches for everyone
(04:21):
involved.
Your homework this week is tomap out every single person
touched by your software, and Imean everyone from your newest
admin to your longest runningcontractor relationship.
I'll bet you find somesurprises.
Next week we'll talk aboutsolution evaluation, but trust
me, this stakeholder map you'recreating is going to make
choosing the right solution somuch clearer.
(04:43):
If you're ready to discoverwho's really being impacted by
your software choices.
Head to fieryeffects.com/choose.
Grab that worksheet and let'sstart mapping because just like
a perfectly planned kitchenmakes everyone's life better.
The right software can lift upyour entire business ecosystem.
I.