Mark O'Brien's Blog
|
Resourcing to the Rescue
July 3, 2008 at 9:43 AM by Mark| After hearing for years how we should be resourcing, we finally bit the
bullet in November of 2007 and had the position in place by this past
January. For those of you that aren't familiar with this practice, my
best definition of resourcing is "the practice of measuring and
planning all billable resources in the company". This sounds obvious
enough, but we went from 6 people 18 people over the course of the past
few years and things that would have been unnecessary overkill in 2005
are essential to operating an effective business in 2008. For a more
detailed primer on resourcing, please check out Chris Butler's article on resourcing. David Baker, the prophet of resourcing, estimates that it takes 18 months from the time a firm makes resourcing a top priority to show its true benefits. The most easily quantifiable measurement for this is utilization, that is, the difference between the amount of work a firm can do and the amount of money that comes in the door each month. David estimates that for a mid-sized marketing services firm (which is the category we loosely fall into, with a few exceptions), the utilization goal should be 60%. Put another way, this means that 60% of our total people-hours should be paid for by our monthly billings. When we took our first pulse on this in October, we found that we were a far cry from that number. Since adopting resourcing, we have come a long way in figuring out why and we've taken many steps, across the breadth of the entire company, to try and correct this. I look at this process similar to gauging and correcting a car's mileage. You might know that your Honda Accord should be capable of getting 30MPG, but the painful truth is that you're only averaging about 23MPG. After identifying the problem, and deciding to fix it, you need to examine all aspects of the vehicle in order to fully correct the mileage deficiency. So, to pull this analogy along, we've popped the hood, tuned the engine up, inflated the tires to the proper pressure, started changing the oil more regularly and replaced the exhaust system in an effort to get things on track. The most important part of this, though, is the way we drive it. How much and what kind of work do we let into Newfangled each month? What sort of expectations are we setting with our clients in regard to deadlines? Are we meeting our goals in a very calculated and determined way? Are we analyzing sources when things go wrong? Fortunately, the answers to these questions are usually positive, and when they aren't, we make it our business to figure out why - because this is our business. If we don't do this well, our ultimate goal of truly serving great clients well is simply unattainable. For a snapshot of the beauty of resourcing, I can offer a fresh experience. I have semi-annual reviews with everyone at Newfangled, and yesterday happened to be a review day. When asked how things are going, one of our programmers had to say that, to him, the biggest change over the past six months has been resourcing. Because of resourcing, his workload has become exceptionally even and predictable, which, as he observed, has allowed him to focus much more on quality as opposed to draining himself trying to meet sudden and entirely unrealistic deadlines. This was hard proof that this concept of resourcing, which could easily seem like management fluff and posturing, has instead shown an immediate impact on the lives of the people in our company we most want to help, those actually doing the deliverable work. There is nothing we can do that has more immediate benefit to our clients than making sure that the people doing the work for them are in a stable environment that fosters ideal productivity. Once perfected, this system will ensure accurate timelines and exceptionally high quality work for our clients and profitability for us. Sounds great, right? |
Tags: resourcing, service, efficiency,
Comments (0)
Firefox is still a little piggy on OS X
March 10, 2008 at 10:27 AM by Mark| Despite really wanting to leave Camino behind, I cannot. Firefox 3 (beta) is still the same hog it always was, taking up 70% of my CPU. By comparison, Camino only takes up to 25% with the same tabs open. There were a lot of other nice features, but I just can't bring my computer to a halt because of a leaky browser. See you next version, Firefox! |
Tags: Firefox Camino OSX
Comments (4)
Announcing Newfangled's Project Anatomy
March 4, 2008 at 1:56 PM by Mark As I will discuss in an upcoming blog post, 2007 was a year of many big leaps in Newfangled's growth as a web development company. One of those growth points was our putting to paper a process guide to our web projects. We have called this the Project Anatomy, and it has already proven to be quite valuable.The purpose of the anatomy was to ensure consistency as we grew the company from 6 to 17 people. As an example, there were some projects in the old days (circa 2003) that I personally closed the business on, managed the project, built the prototype, programmed the site and put it live on the server (NEVER did I design anything - we weren't stretched that thin). Those were, honestly, really fun days. The nice part about it was that I learned a lot with each project, so I just automatically got better and things improved. Fast forward to today, where we have 17 people, any 7 of which will have involvement on a given project through its initial development prior to going live for the first time. That represents a lot of moving parts, and a lot of dangerous chances to make mistakes and not collectively learn from them. Fortunately, this problem also has opportunity buried within it. Our opportunity, of course, is to increase our learning seven fold. We could either wallow in inconsistency, repeating the same mistakes over and over again because we aren't talking about it, or we could assemble an ever-improving document that could guide all of the major components of our web development projects. Given our experience with this so far, and the many changes it has already gone through, I think we've landed on the correct side of this problem. The Project Anatomy will most likely be different again next week, but it currently does a pretty thorough job of representing the major and minor stages of a web project for a 25-45k site. Since most of this is not proprietary to Newfangled, I welcome anyone to use it and make changes as they see fit. Here are a few examples of the small details that we have captured as a result of our collective learning. You might want to follow on with our Project Anatomy document.Prototyping: DNS and process review with the client Clients are always in a rush to go live at the end of the project and they usually don't know how to get the necessary access to point their domain name at our server. Clearly, neither of these things are major discoveries. Our slight shift in process, to instigate the DNS conversation at the end of the prototyping process (which is the first major stage of the project) was a big deal though, at least for us. It is just one small detail that is going to make our next project go a little smoother. Integration: 301 redirect review Integration, the fifth stage in the project anatomy, is the stage in which the client adds their content to the programmed site while we apply the approved design. Most sites we build existed previously, and sometimes the legacy site had really great search engine placement. Since our system is most likely going to have different URLs than the old system the clients are going to need to know what 301 redirects are (here is a great thread on them, if you aren't quite positive) and how they should be setting them up, using NewfangledCMS's new 301 redirect management tool. This little reminder will ensure that we at the very least have the 301 conversation with our clients and that they will be properly educated in order to make the right decision. This is a great alternative to all of us having a big *gulp* moment 3 months after the new site has gone live and the client just realized their old ranking really mattered. Design: Home Page Designs: Internal review with PM, UX, Programmer and Planner Eric always wants to see what we are up to with our designs. In the heat of the moment, we often forget to include him in the design review process - no more! Well, kind of. Now we are ensured that a planner will always be included in design reviews. According to the role definitions in the Project Anatomy, that means the Eric or Chris will take part and that our client will benefit from not just the designer's attention, but the reflection and critical thought of 5 Newfangleders at this stage alone. For us, the Project Anatomy is riddled with project management wisdom that we've accrued over the years and continue to build on. Like so many other things we've figured out over the years, it has become an essential part of our makeup. |
Tags: WebDevelopment Webprocess ProjectAnatomy Projectmanagement 301redirects DNS
Comments (0)
Not every day is like BLING day
March 4, 2008 at 3:56 PM by MarkAble Parris, the new minister of office culture here at Newfangled NC, has inaugurated a new tradition that is sure to spread like wildfire among mid sized marketing services firms across North America. This is the kind of thing that brings Robert Scoble to tears, makes Jeff Bezos jump out of his seat and proclaim that the world will never be the same... this, my friends, is BLING Day.
|
Tags: BLING AUDACIOUSBLING
Comments (10)
It's the prototyping, stupid!
February 25, 2008 at 9:18 AM by MarkA few weeks ago Eric and I attended the ReCourses/Win Without Pitching New Business Summit in Nashville. David Baker's events are great for us; the attendees are often times principals of mid-sized agencies and, since our shop is structured a lot like a mid-sized agency, his advice is almost always directly applicable. During one of the sessions, David was talking about specialization, and how you need to be an expert in a very unique niche. For example, being a "marketing" expert is not enough, and it is sort of a fallacy. Being an expert at marketing equestrian products to mid sized farms in North America, now THAT is a specialization. David asked an open question to the audience, "What are some examples of specific knowledge that you have as a result of being an expert in your field"? I'm not particularly afraid to speak up in a crowd of people, so I raised my hand. Newfangled specializes in working with agencies on their and their client's websites. I cited the example that we have learned over the years that when agencies don't let us have direct access to their clients, the communication breaks down and the project doesn't go well. This was the third response to David's question. After my somewhat appropriate, but not spot on response, he looked a little flustered. Eric then chimed in and said something like "Newfangled has learned that without proper prototyping, communication about a web development project is flawed". UGH! Humiliation! Of course, It's the PROTOTYPING, stupid! I knew that. I could have said that, but no, my moment in the sun was squandered on explaining some low level detail that didn't really engage anyone, and Eric triumphed by stating our old party line. But man, it is a really good line. It is so tightly integrated into what we do, it is so central to our universe, that I forget that most web projects managed by other firms never even see an interactive, web-based prototype. I spend hours ever day telling our "clients to be" (to borrow a phrase from Blair Enns) about how prototyping is the bedrock of Newfangled, and it really is. Sure, we have a great CMS, we are hyper devoted to great and conscientious customer service, we have a lot of smart people that build and design excellent websites every day, but the prototyping is our real differentiator. It is at that stage, which for us is the very first stage, that we truly shine as brightly as we can as web developers. The main reason for this is freedom. Prototyping gives us and our clients the freedom to suggest anything, and try everything. Because the prototype tool is based on our CMS, it has no visual design elements (hence the Grayscreen) and we are just basically mocking up functionality without actually programming it out, we can have changes made to the prototype within hours of a brainstorming session. That kind of quick turnaround fosters a lot of brainstorming - and we love it. Imagine that, entering a web project with every possible option available to you. It should sound wonderful and very scary, which brings me to my second wonderful attribute of prototyping - consultation. Again, prototyping is the very first stage of the project, and it is also the stage that has the most Newfangled eyes on it. On average, seven different people here, including most all senior staff, take part in the prototyping process. I'm not much for numbers like this, but that is the equivalent of over 60 years of 7 different and unique perspectives on web development! The Grayscreen Prototyping stage is our opportunity to take advantage of our collective experience and use it (via internal debates, sometimes lots of them) to basically take the most educated guess possible as to what your site should be doing. Once the prototype is done what we have is analogous to the blueprint of a house - it is a very detailed, mutually agreed upon set of plans. This seemingly needless and time consuming phase that many other developers plain skip actually ends up accelerating the overall time line. That is because the design, programming and copywriting can all take place simultaneously after the prototype is done, because everyone is playing from the same rulebook. Not taking our own best advice, we strayed from prototyping a few years back on some projects that were so simple, we thought they didn't need it... that will NEVER happen again. Prototyping is here to stay, and I believe it is the most essential part of Newfangled. |
Tags: usability WinWithoutPitching prototyping informationarchitecture DavidBaker consultation ReCourses BlairEnns
Comments (0)
commoncraft
January 27, 2008 at 9:15 PM by MarkOn the subject of defining things, commoncraft has done a great job at describing the who, what, where, and why of blogging. They've also done the same for Google Docs. As a company whose foundational philosophy is to make complex things simple, Newfangled salutes commoncraft for absolutely nailing it! How did I hear about commoncraft you ask? Naturally, I found it through my Google Reader feed for Smashing Magazine. |
Tags: blogging commoncraft googledocs
Comments (0)
Taking the plunge - Part 4 - Useful definitions
January 22, 2008 at 8:45 pm by MarkWhat, you don't know what Furl Digg Stumble del.icio.us Diigo Permalink Technorati Twitter Stumangati and Ficklewink are?!?!?!?! Yeah, me neither - here are some definitions to help us... Here we have a few brief, simple and generalized definitions of some populare web2.0 tools. Each of these tools probably do about 1,000 more things than I mention here, but my interest is to give you the gist of it. If there is anything that I've gotten plain wrong, comment and tell me about it! Permalink: This is a URL that sticks with blog entries even after they move into the archives from the blog's home page.
Furl: Furl is a lot like del.icio.us, except not nearly as used. So, I'm going to stick with del.icio.us.
|
Tags: diigo furl web2.0definitions stumbleupon del.icio.us permalink reddit digg technorati
Comments (2)
Taking the plunge - Part 3 - Google Reader
January 22, 2008 at 8:15 pm by Mark| As I mentioned in my last post, I received great advice from Chris that in order to blog well, you had to read great blogs. That makes good sense, but how do you find great blogs, keep up with them and keep track of the new ones that are sprouting up every day. It turns out, it's easy - with a little help from your friends. Google Reader, to me, makes web2.0 possible for me. When hearing about people that kept up with many tens of blogs that each had tens of posts a day, I always wondered - how do they find this stuff? There are other questions that pop up after that one is answered (of which you'll see a few below), but for me, finding it was the first mystery. I started with seeing what my peers were doing. Google Reader let's you not only easily peruse the blogs you want to keep up with, it lets you see what blogs your friends are reading and which ones they have specifically designated as share-worthy. Starting with Chris and Eric's blogs, I quickly spidered off and found others that I am interested in. Here is an excerpt from a Google chat between Chris and me last night: 9:47 PM me: how many blogs are you subscribed to? Christopher: 71 9:48 PM me: omg HOW?!?!?!?!?! that is so depressing ugh 9:49 PM Christopher: why depressing? 9:50 PM me: I have like 20 and there are endless blogs to read Christopher: hah yeah, but remember, one of the key things is knowing how to skim well and, you have to grow into it gradually i've been using rss for years now and constantly pruning my subscription list 9:51 PM subscribing, unsubscribing, etc. so it takes a while me: ok Christopher:
whats more important now is that you get to know the kinds of blogs you
like, and why, and which ones are important for you to read me: yeah Christopher: for example, though he's all huge and what not, I've decided that Scoble is not really an important one for me to read 9:52 PM so I gave him the cobra a while back 9:55 PM me: I added him today 9:56 PM I'm adding a bunch and will then prune out Christopher: that's the way to go As you can see, Chris (and Eric) are excellent resources. In summary, Google Reader is a great blog aggregator. There are many out there, but I find it to be too good to continue shopping. |
Tags: web2.0 EricHolter ChrisButler GoogleReader Blogs
Comments (1)



















