Michelle, the consultant
posted in Consulting |Someone mentioned to me that from what I write on my blog, she wouldn’t know what it is that I actually do in my consulting work. I kinda thought that was surprising, but in thinking about what I write, I realize that people could get the wrong idea (or, more accurately, fail to get the right idea.) And, I guess truthfully, the blurb on my consulting site is kinda dry. Gotta work on that.
So, what do I do? I think of myself in these terms: I educate, facilitate, mediate, and problem-solve.
For one client, I am their technology go-to person, since they are really small, and have no tech staff. I don’t implement much for them (although in a pinch, I’ll set something up, or fix a specific problem.) But I help them plan their technology initiatives (a new database, a new website, etc.,) help them find the vendors that will do the work by helping them craft good RFPs. I answer all of their tech questions, and solve pretty much all of their tech problems (mostly by helping them figure out who they should call.) I’ll be the project manager on their big new client database project, and help them think about how far to dip their toes into Web 2.0.
For another client, I helped them vet vendors for their new website, taught them the difference between Joomla, Drupal and Plone, and I helped free them from a vendor who was particularly egregious in their hosting charges, among other things. ($1200/month for an old and therefore crappy custom CMS and not much support. I. Kid. You. Not. I myself wrote a custom CMS a long time ago that would be considered crap now, so I don’t blame them for that, but the charges???)
For a third client, I helped them translate their ideas about what they wanted their website to do, to things that could actually be implemented in a CMS. I helped them vet CMS vendors, make sure the CMS that was chosen could do the complex job they were asking it to do (some were not up to the task) and am the intermediary between the current web vendor and the client, lending my expertise as needed, and helping to move the project forward.
I think my clients benefit from one particular thing that I think is pretty unique. Although I am deeply experienced and knowledgeable in implementation of technology, from networks to web applications and databases (I really know how DNS works, can write a left outer join in SQL, and know the difference between REST and SOAP) since I don’t do implementation or coding anymore, I’m not wedded to one set of technologies. I can bridge the gap between technology vendors and clients in a way that is pretty unusual, and, honestly, that I’m proud of. I know when a vendor knows their technology, and when they are blowing sales language at me, and might not be up to the technical task. I can evaluate previous projects based on what I see is the underlying complexity, and figure out how much experience a vendor has had with a particular set of problems. I know when a technology is really appropriate, and when it’s not.
I have other kinds of projects as well - those that use my talents somewhat differently. I do a ton of technical writing, and I have become the “documentation facilitator” of the OpenMRS project - it is an open source medical records system, designed to serve clinics in low-resource areas (such as sub-sarahan Africa) that treat patients with HIV/AIDS. Since we’re starting with the developer documentation, one of the coolest things about this project is that it’s making me learn Java and Eclipse, plus get my hands dirty with Tomcat. Yum! I love learning new stuff.
I like the range of projects I do. I’d like to do more of all of it. I’d also love to consult with for-profit vendors who are thinking about dipping their toes into offering support for open source projects, or open sourcing their software.
OK, enough of that. Now back to our regularly scheduled programming. :-)
Tags:consulting nptech
