July 19, 2013
From time to time, even a Salesforce admin needs a vacation. But for many of you, you are the only admin at your company. So how can you take time away during business hours, and still give you users the support that they need to do their jobs? In this post, I’m going to share some of my tips for a successful admin vacation.
It may seem obvious, but the first thing I do is to communicate that I will be away. By informing those I work with regularly that I will be out of the office, the hope is that they manage expectations and let me know of any urgent issues before I leave. I also provide clear information in my Out-of-Office alert on when I will be back, and what sort of access to email I will have while I am away. Finally, I include a link in my Out-of-Office to submitting an internal Salesforce ticket, so that requests that can be handled by others end up in the right queue.
read more »
July 12, 2013
Happy Friday readers! Apologies for last week. I forgot to let you know that FBtF was taking a holiday for a long July 4th weekend. We had some great weather & enjoyed time in the sun. We are back now, and a new Friday brings another blog post, and this is one that I’ve been wanting to write for awhile.
As the long-time readers will know, my first job working with Salesforce was a bit like the wild, wild West. We didn’t use a sandbox to test changes. Trying out new features (like validation rules) were trial-and-error. And we didn’t use the description fields.
read more »
June 28, 2013
As an ‘adult’ (in quotes, because I still don’t really feel all that grown-up), one of the questions that you inevitably get when meeting new people is “What do you do for work?”. As a Salesforce administrator/developer/business analyst, I’ve struggled to come up with an easy way to answer this question. In fact, I can explain the jobs of pretty much everyone I know (including the guy who makes DC to DC converters), but I still struggle with my own. So what’s the perfect Salesforce admin elevator pitch?
Image via commons.wikimedia.org
read more »
April 13, 2012
(That was supposed to be a play on words – teaming/teeming – but not sure it came across that way.)
Most companies start out with one Salesforce.com resource (or maybe even half a resource). But as adoption of the platform grows, so does the need to have a larger team to support it. The question that a lot of organizations struggle with, is what does that team look like & how do I find the best resources to staff that team?
A team typically starts out with an administrator – someone who does end user support, new user set-up and all other standard functionality. This is that first Salesforce-specific employee, and it may not even be a full-time role. Once the demand grows beyond one person, the next position you may consider adding is a business analyst or two – someone who can understand & translate business processes to functionality within Salesforce.com. Somewhere along the line, you will probably want to hire a project manager or similar role who can act as a team leader. And if you are lucky enough to have the budget, and find someone who wants to work for you, the addition of a Force.com developer could bring huge impact to your organization.
Of course, all of this can vary based on your business, your maturity as a Salesforce customer, or what projects are on your Salesforce roadmap. I believe that the key is not the titles or who reports to who, but getting the right skills in the door to do the work that needs doing. And if you are lucky enough to have Salesforce skills, remember that you should always love your job.