As a team with our customers, we are continually updating lots of records at once. As much as we love Salesforce, sometimes it needs a little help with this and that’s where Gridbuddy comes into play.
Full Disclosure: This is a continuation of an occasional series of apps that we either use and/or have recommended to clients. Some of these amazing ISV’s allow us free access within our own system so that we can understand its functionality and how it can apply to our clients. Our relationship with Gridbuddy goes back many years and if it were a dog, it would be old enough to order its own beer. To that we say, “Cheers!”
What is this Again?
I could talk about the functionality of Gridbuddy, but I think this video does a great job:
Instead of talking directly about features, let me discuss with some internal examples.
Yes, Salesforce has an excellent reporting and analytic tool. There is no reason why not to continue to use that function. Even if you have Salesforce Analytics (Wave) or Tableau, you will probably still work and use the built-in reporting tool. But that’s another blog post.
A key aspect of Gridbuddy is its inherent ability to show detail of not just the parent, but also the children. While it is not a pivot table or matrix, the reporting tool and its summary abilities are not there, but it does have the ability to show good shares of data in an excel file. And if you need the detail, that is helpful, as well.
Ever try to report on a long text area fields? Go and try it in Salesforce reporting. It truncates it! Gridbuddy? Nope. All those fields in all there wondrous glory, all formatted like you left it. Easy-peasy.
Another feature we like is that the export function also breaks apart the children into separate tabs and includes the salesforce ID’s. This makes mass editing and working with data loading tools easier for an admin.
Respect the Record Type
It may seem not a large deal but if you have record types you know that its important to protect the fields and field accessibility layered into our app. While salesforce does a decent job of protecting us when using the standard page layouts, its important that other editors also enforce those rules. Gridbuddy will enforce your record type’s field protections and so even if a user attempts to make a mass edit – the system will stop them from saving.
Thinking WAY Outside the Box
Unfortunately we cannot show a screen shot of this but there was a client that wanted to center their salesforce usage on only Gridbuddy screens. Fortunately it is possible with a some ingenuity to allow your users to do almost all of their day-to-day effort using Gridbuddy. For example:
Use Visualforce and the Tab function to create a tab for each grid in the sales process.
Define your grids so that there is a grid for each stage in your opportunity pipeline.
As Opportunity stages change, the records will naturally flow from one grid to another.
Consider using workflow actions to record completed call activity records based on information stored as fields on the opportunity.
Consider creating a call back date field on the opportunity so that each grid is sorted based on a call schedule.
There are so many options to consider for this tool. Again Gridbuddy does a great job of defining their core components but we wanted to highlight some features that are typically not shown in the standard tool.
I know it seems crass and some of these are probably will take some time to implement but when we work with clients we see these five actions coming up as consistently not done. And so you have to ask yourself, “Self, SHOULD I be doing these things?” We think so….
Keeping a backup
If you’re an old school IT person like myself, then you know how important it is to maintain a backup. But you are not typically using the backup to restore the whole database. Nope. You are using it to restore someone’s goof up (typically you’re own), or you need to move data from one system to another. So many great uses of a backup.
The easiest method is to use the Data Export feature in Setup. Please set up a schedule and store it somewhere safe. If you are not storing attachments, the database file will stay relatively small. But you will get .zip files containing one CSV file for each object in Salesforce. Attachments are a bit more exciting (much larger files) but that’s a conversation for another time. Alternatively there are some great ISV partners that sell backup solutions. Spanning is one of those examples, as well as Backupify.
Don’t ask Salesforce to restore your data. It gets pretty pricey.
Cleaning out old reports So you’re the admin that, like the Fairy Godmother, has created a report for every user needing every kind of situation report imaginable. Congrats! You’re a rock star! You really need to teach you’re people how to create their own reports. Let me ask a question: how often are they being used? You, and probably a good block of your users, are having to sift through all these reports when they are searching for the ones that really matter. There is a report type available that can show you the times that a report is run as well as other statistics. Run these every so often. Move the unused reports to a folder that only Administrators have access to, for a while. If it’s not missed, delete it!
And then while you’re doing that – train a few super users to create reports. Honestly. Huge time saver.
Tracking field usage I gave a talk about the habits of a successful admin. One of my points is the that it’s not necessarily duplicate data I despise but, bad, missing or useless data! Do I really need to store that account ABC Inc. received the 2013 Christmas Card? Go and track down those fields that are routinely blank, are used by one person or have outlived their usefulness. Then get rid of them! (You do have a backup, right?) We find Field Trip particularly easy to work with and full of usefulness.
Listening to your users We recently performed a one-day workshop for a client talking about their roadmap of work. Now while I discuss roadmaps below, let me discuss something more important than that: are you listening to your customers ie: your users? You may have the whole world figured out but if you’re users are asking for “X” and you build “Y”, it will be similar to building a schooner in the middle of the Sahara. So pretty and utterly useless.
Find a way to regularly discuss what is being built and get feedback from your user base. Build it in. Even Salesforce’s Project Managers are tasked to “retire” a certain amount of IdeaExchange points every release.
Maintaining a roadmap of work What are you working on this month? What about next month? Have you thought about what will be necessary 6-12 months down the road to match business needs? Even with a small deployment of the tools, planning for the needs in advance can make a difference in the quantity of time necessary to deliver those goals. Some of us admins are part-timers, so we have to be extra careful to deliver the goods while we do other things.
It could be a simple spreadsheet or something way advanced, but in the end you should be able to answer:
What are we working on this month with concrete details?
What is on the plan for the next 2-3 months?
What are looking at for next 6-12 months?
Write it down, share it with your user base, get feedback, then alter accordingly.
Why not chat with us?
We work hard for our clients to deliver something amazing each day. Why not contact us to learn how we can help you?
Baseball managers, in my opinion, are probably more pivotal to the vitality and success of a team then coaches in other sports. Why? The season is long and with spring training added, these group of players are looking, and hopefully listening, to this person far more then football, rugby, hockey, etc…. If you watch the players you can get a sense of what the manager is like. Are they loose and comfortable? Are they regimented? The term “Skipper” is often used for Baseball managers for a darn good reason.
Joe is known as someone who can relate to younger players easily and create a comfortable atmosphere to play. And yet his teams know when to perform. Look at this guy – he is no spring chicken.
When Joe left the team, it made me wonder about when business leaders leave and move on. This may sound fairly obvious but the best people always move on eventually. Its rare to the level of discovering a purple elephant with a unicorn sticking out of their head for amazing people to stay with one company forever. An organization needs to be ready to handle this and also to understand what occurs when that happens.
If the leader was terrible then few of what is being discussed will apply. Hasta La Vista Baby! Please don’t let the door hit your rear end on the way out. None of what you are reading will apply.
First let me ask you this: is the leader of the group the one with the title or the one everyone looks at when there are questions? For those in power are you sure you’re the leader or the gatherer of people and information?
Second, there are functional leaders and technical leaders. In the technology space, its purple elephant rare to have them be the same person.
Back on point what happens when the leader leaves? This is highly non-scientific and I’m certain there are many articles that discuss this in multiple layers of psycho-blabber but let me address it in my own way.
Guess what, its going to stink for a while. That’s just the way it is. There may be some deliverables and requirements lost when they leave and as such its important to rally the rest of the gang around and get everyone recounting everything they know and what was on the pipeline.
Does your group need a new leader or can someone else from the group take that role over effectively? The old pizza ordering trick works well. Order pizza and see who takes charge of figuring out what to put on it. Still have chaos? Better get a new leader stat.
What About an Interim Leader?
This may seem strange but maybe the right solution is to bring in or promote someone to be a leader for an interim period of time. Everyone knows this person is here for a relatively short period of time while a permanent replacement is found. There are quite a few churches that do this. When the pastor leaves, the denomination sends in an interim pastor to lead the church while the search committee finds their next permanent replacement. It gives everyone a chance to breathe and not be forced down a timeline.
Lets break out the Boy Scout rule here in this situation. Are there systems and data in place to understand what needs done first, second, and third and when? It may not be fancy but some documentation and planning would be helpful. I would hazard a guess that just as many organizations use documents and spreadsheets as project management applications. Does that mean its wrong? As long as the data is accurate why not use that until a reason is identified?
If its a technical resource and its the knowledge you need, work the network. No one person knows everything about one subject. There is always someone smarter or at least knows as much as that person on your team.
Know There are Going to be Mistakes
I wish I invented this line but I overheard it many years ago, “No babies are dying if you make a mistake”. Unless you are in pediatrics then this is probably true. Mistakes are human and are going to happen no matter what occurs. In fact more mistakes may occur while the team regroups and finds themselves. Get over it. It happens. Focus on fixing them and preventing future ones. Information is going to be key and having all the information out in the open is critical to preventing future mistakes. Be a child and ask, “Why?” more times then normal. Be certain that everyone, and I mean everyone, fully understands what is required while the group rebuilds trust.
It May be Awesome
No matter how amazing that person was in the group, the next person may be even better. Its not the end of the world. Be positive. Help. Be ready for amazing.
In the end leaders and followers leave. Sometimes its for good reasons and others times its for bad ones. Just about any group CAN survive that but its up to the individuals to be ready to put their effort in and not give up.
Want to talk more about Salesforce? Get in touch with us:
On the last day of Dreamforce I took a fall while delivering my session. As far as I know, this is the first speaker-related injury in the history of Dreamforce. That effectively ended my week early and I missed a few engagements because of it.
When I was home the pain wasn’t going away and me being the stubborn sort that I am finally succumbed and went to the ER in my hometown. Now I don’t know if the ER’s near you are like the ones near me but hospitals seem to be spending serious shekels to improve their experience. There are billboards in the neighborhood showing average wait times so that you c an select the ER with the lowest wait. As a note – Starbucks if you were to start placing wait times in nearby shops I would consider that a wonderful public service. Just an idea.
Into one of these “modern and efficient” ER’s I go thinking that based on all the advertising my experience would be fast and efficient and my needs, being somewhat basic, would be an easy case and I could go about my day.
Oh. Me. Of. Little. Knowledge.
What transpired was 4-5 hours of the oddest and bizarre process management in my life. And after experiencing it I began to realize that many Salesforce deployments and consulting projects go through a similar process. To be honest it scared me and made me realize that we all could do better if we recognize the phases.
Phase 1 – Recognition
I walked in the door of the ER and the receptionist takes my name and assigned me a medical bracelet with a number. I then fill out a very short form with my name and complaint. After which I am asked to sit down with everyone else in the waiting area where the following is happening: a woman is hacking a lung into a small bowl, a child is wearing a surgical mask due to his disease, a younger couple both looked like they were in a fight and needed patching (I don’t think they fought each other), and a poor elderly lady who was just confused and enjoyed yelling had something wrong with her leg.
All of a sudden I felt small and very much low priority. But I had my laptop, a place to plug into, free wifi, and a coffee machine so I decided to stick around. If it wasn’t for the MRSA probably flying around this wouldn’t be a bad place to work on a regular basis actually.
Let’s correlate this back to Salesforce. This is someone talking during the sales cycle. When someone talks to sales we get your name, address, phone number, and hopefully chief complaint. Was there a deep dive? Did they ask for my insurance cards/some substantial background info? Nope. They just wanted me in the queue.
Phase 2 – Triage
After about 45 minutes I was shown into a small room where an ER nurse performed triage. Was I breathing? Yes. Was I about to succumb to the Black Death? Nope. Great. Back in queue with you! After I left the room, where I did my best to entertain them hoping for fast service, I’m certain they all snickered and wondered how long I was prepared to wait it out since their shifts just started and needed some normal entertainment. Maybe not. It was at that point I figured out where that counter on the billboards stopped. It was right here.
When we are working with sales opportunities we need pull others in with some technical expert to do a clinical triage of your situation and see if we can help you. Its usually on our clock and schedule unfortunately. One of my mentors had a saying, “If you’re going to fail, fail fast and move on!” I wish more Salesforce people would do the same. Just say it’s above, or below, your skill set and move forward. Going 14 rounds before determining that you can’t handle this or do not have the manpower to effectively work the project is not helping anyone.
Phase 3 – Cash, Check, First Born, or Kidney?
About an hour passed between triage and the next visit by someone. During that time the poor lady hacking a lung was becoming far worse and I believe the whole room was hoping she was next, the couple in the fight that walked in together we’re being seen at different rates through this process, and the kid with the mask was just looking more pale. Eventually a Physician’s Assistant came out to examine the hacker to say something encouraging but then quickly left the lady in the waiting area.
What came next for me was nothing short of hilarity. A woman came with a push cart with a laptop, external screen, card reader, signature pad, and a huge battery powering it all to where I was working. Her job was to get me into their EMR and setup a method of payment. If you checked into a hotel the process is similar. Or at least that is what I thought.
The number of screens to do what I thought was a simple admit was hilarious. I counted 12. And the number of different user interfaces was at 5. That included the post office Zip + 4 lookup website. And we’re there workarounds? Oh yeah. My insurance was in a different class so it had to be searched with a special option to find it but it took her a few moments to realize that detail and then it just “didn’t work right” so she kept moving forward.
You have to give hospitals credit, at least they ask for a method of payment before providing any substantial services. As consultants we have a signed agreement and then we hope you pay in many cases. There are those cases that choose not to pay for a variety of reasons. If you’re a consultant it’s just the way it is; it may not be your firm’s fault but it happens. And not being paid is similar to riding a motorcycle. Its not if you will fall off the bike but more WHEN you will fall off the bike. One day – someone is just not going to pay the bill.
You could also tell that someone from the hospital’s IT department was quite proud of their Frankenstein mobile admission cart. They were all over the place as I found out. And I’m certain that the “Franken-ish” of the solution was not entirely the fault of the IT department. Many software packages in the healthcare space are closed off to innovation. Want to make a change in software? Call the vendor, worship their wonderfulness, be happy when they say the change will take 3 months to be put in place, and have a huge minimum fee to cover it. That is if they respond. There are so many hospitals trying to get EMR’s in place and working these days it’s more of a “scorched earth” policy then a helpful one. They are just trying to get these new hospitals standing that many items and requests of current customers are falling to the wayside. And the idea of an open API and Hipaa do not go hand in hand. (End rant)
Back to our friend the payment agent. Here she is trying to use multiple different systems that barely talk with each other to enter my details in the hope they pay. Her frustration was fairly high but at least she got to walk around while being frustrated. Proponents of the standing desk unite!
Phase 4 – Diagnosis
Now we’re on hour 3 (or 27) of “Dancing with the ER Stars.” Ms. Hack-a-lictious is joyously out of the waiting area much to everyone’s happiness. The poor couple in the fight have split as they lady was seen but the guy was being pushed so far down the queue he just gave up and left. The kid is still there but the PA did come out and it seems that he is just there for an “he’s ok” rather then “he’s falling apart”.
That same PA finally came up to me in the waiting area. She apologized for the wait and decided to do an examination in the waiting area. Say what? Good thing I didn’t show up with a hernia or something….
She decided that an X-ray was needed and in fact activities started speeding up after this. Let’s call this in Salesforce speak an “active project”.
I am finally called up for some diagnosis. That’s more being shown into the X-ray room and get a few pics taken. I am encouraged to gyrate around on a table in different sultry positions that can be found in many a men’s magazine so that everyone can gaze at the awesome that is my knee injury. With photos! It will be on TMZ later tonight!
After which where am I sent? Yup. Back to the waiting room. Why not? I’m getting well acquainted with my new best friends for the past few hours. And the coffee machine makes something approaching the flavor of coffee.
If you’re doing a Salesforce project this is typically the “kick off”. We’re finally getting inside and understanding the extent of the problem that we’ve signed on to help with. And like going for an X-ray, we take some pictures and gather notes but then we have to go away and digest what we learned many times. Trying to come up with solutions and attempt to fix immediately is usually a bad idea. We may ask your company to answer all kinds of questions and talk about what are your pain points and solutions for a while but on the spot solutions are rare and more importantly rarely work.
Phase 5 – Treatment
The PA said before that I will probably not be shown an ER room due to volume and my problem. Fine. Not a problem. Just tell me that I’m not doing irreversible damage and how about a small pain pill please?
Eventually I am actually shown a bed and two nurses start to do some things. First I’m fitted for the worst performing knee brace in history. Stand up – brace doesn’t work. Walking – doesn’t work. This is awesome. Second I’m fitted for crutches but apparently they thought I was Frodo instead of myself so the position they have me in is more “Hunchback” then “Hunky”. I get it. You want me out of here. Guess what I do to! It’s now four and a half hours and I’ve been here since 1:30 on a Monday afternoon. But I did get a script for some pain meds as well and I’m not going to lose my leg tomorrow.
Here’s what concerns me when it comes to Salesforce consulting. My team and I work hard to avoid this but there will always be projects where people just want to move forward and be live. This may seem harsh but try to avoid that idea. We are not looking to enhance our billings. Instead we want to be certain that your go live is smooth. The worst case scenario is a system made to go live without testing and making certain it fits. A bad fitting or poorly designed knee brace is worse than none at all.
If you’re a Salesforce consultant many of the above may sound familiar and you may be saying what I was, “there has GOT to be a faster way to do this!” I’m certain there was in this ER and like many businesses any current process is a merging of “that’s the way we always did it” with “here’s a few ideas to make this easier” and “check out this cool widget!”
Are you as a business ready to throw away everything and rethink the process if it will realize you dramatic throughput? How much is that worth to you?
As a consultant how much time are you willing to give before getting paid to be certain that projects go smoothly?
Is it better to try to move a project from start to finish rather than the process of collect and gather, consider, propose, and implement?
Just a few thoughts I was thinking will limping home on my crutches…..
Want to talk more about Salesforce? Get in touch with us: