Category: Business


Document Surgery

==

Leatherman 80030003 Squirt P4, Inferno

==

Things with the job have been okay lately — sometimes really good — and people are telling you how happy they are that you’re there. Admittedly, though, this is one of those low moments of the job that you don’t want the people you meet at Christmas parties to know you do. You’ve constructed a 26 page report for some high-level people (think three levels above your manager) and sent it to the copy room to make 15 copies. Only, you get there to discover that you’ve inexplicably inserted a blank page in the document that’s not supposed to be there, following just after Page One.

You consider editing it and reprinting, but reject that in favor of ever-so-carefully pulling the offending page out of each of the 15 packets, thus messing up the pagination, which you don’t think anybody really reads at 6pt type anyway. You spend the next half-hour pulling the pages out, wondering if anybody saw the mistake in the email you sent last night and whether it would have been just as easy have had the document reprinted. You get to the end of the pile and notice the little shards of paper littering your desk, left over from the corner of the ripped-out pages. You wonder about the rest of those shards still tucked away up underneath the staples of those packets and how they might look on the expensive conference room table at this afternoon’s meeting.

Remembering the snub nose pliers on the Leatherman in your pocket, you let out a sigh and begin to carefully pry apart the quarter-inch of paper above and to the left of the staple. You’re not sure if it’s low blood-sugar, caffeine jitters, or just plain nerves that causes your hands to vibrate at the Concert A frequency of 440 Hz, but another 15 minutes go by before you’re finished and you can look for some other, more meaningful task to justify your employ.

Seeing that I left off my last entry by noting that getting interviews is the other half of the battle, I figured I’d share how I’ve been doing that, too.

One of the really interesting things about the job search is how much it relates back to sales and marketing. I’ve been going through outplacement classes (“sessions” sounds too therapeutic) over the past few days at my previous employer. They’ve been excellent. A career manager from Lee Hecht Harrison has been on site to guide us through the transition process. The most effective thing she’s been able to impart, aside from her 40 years of human resources experience, has been a framework for undertaking a new job search. This, I think, is the scariest thing about losing your job: not knowing where to start. There are résumés to put together, contacts to call, people to meet, portfolios to build, emails to send, searches to run, clothes to buy, research to do…the list goes on. I already had been passively looking for a new position since November — thinking something was going to happen to my team sooner or later — but, quite frankly, I just don’t think I would have gone to all this trouble if the necessity hadn’t been foisted upon me.

LHH has done a world of good by putting the job search in the context of project management — a topic that a lot of us business and technology geeks can relate to. You set your goals, design a plan, build milestones, track your progress, execute well, and assess its completion. All straightforward stuff, and not a big deal to people who have been drilling this stuff for the last several years. We’be also been learning quite a bit about Sales & Marketing because so much of a job search is exactly that — marketing and selling your skills and experience to meet potential employers’ needs. This has been both eye-opening and familiar to me at the same time.

For of my professional life, I’ve been working in a sales context, and that has given me a lot of exposure to what it takes to be good at sales. My work with the customer relationship management (CRM) systems that the sales teams use to organize their day has taught me a lot about successful selling. In a few words: it’s all about follow-up. If marketing campaigns (like that credit card advertisement you threw away yesterday) are the first touch, good selling is following up that message with a phone call, visit, or email. CRM systems essentially boil that process down to a workflow and a repository. If a CRM system is working correctly, it’s helping you remember the name of that guy you exchanged business cards with at that tradeshow two months ago, who asked you to give him a call sometime. Siebel has created a vast enterprise building these systems.

The need for successful follow-up became apparently clear to me once I started getting face-time with hiring managers. Promises to forward résumés, make phone calls, and send emails got lost in a sea of buisiness cards and handwritten notes. I had toyed with the idea of building a tracking system for this actviity, but quickly realized that a.) it would drain a lot of time that I need to use more effectively and b.) this functionality already exists with CRM, and there are open-source systems out there to use. After a bit of searching on SourceForge, I rediscovered SugarCRM: a PHP and MySQL, open-source CRM platform. I set up a subdomain on Simplificate and installed the app — SugarCRM was literally up and running within an hour, and I was reaping the benefits inside of a day.

SugarCRM uses a very standard object model for tracking the selling process: companies are organized into Accounts, people are associated with Accounts and identified as Contacts, potential sales are organized and associated with Accounts and Contacts as Opportunities, and any of these objects can be associated with todo items called Activities. When you log into the system, you’re presented with a dashboard that consolidates this information into one centralized view. Open opportunities sorted by dollar value are listed, along with activity reminders (did you call John Doe?) and a calendar. Your opportunity pipeline is graphically shown using an interactive barchart using Flash that you can use to drill down to more information. Pretty slick for a free application. SugarCRM is not without its bugs: there’s the occasional sort-order problem, an irritating display problem that shows PM times as AM, and general usability could improve (tab order and readability on forms, for example). But it does the basics, and does them very well.

I noted that sales and job-hunting have a lot in common, but there’s one key difference to keep in mind when using a CRM application. The goal of sales is to sell as much product to as many qualified leads as possible. The goal of job hunting, however, is to sell one single product to that one, very special customer.

First pass at a cover letter

I would be certifiably nuts to send this to a real prospective employer. But, as a creative writing device, it worked to bring my voice to the forefront and make me sound like a real human being. This kind of in-your-face audacity is probably a touch too harsh, but I can’t imagine having a little backbone as a bad thing. What do you think?


Hi there.

You don’t know me, so let me introduce myself to you. I’m the potential employee that was recently laid off from a technical analyst position for a large multinational company. I want to write you in such a way that will captivate your attention and make you think that I’m a witty and intelligent person. This, of course, may or may not be true — I could be a total coward with some tech skills — but, I guess you really won’t be able to find that out until we sit down and talk face-to-face.

I noticed your ad in/on the paper/web that you were looking for someone with my abilities to help propel your organization to reach its goals. I think it was wise for you to advertise the need for such a person — that is, rather than look for someone to bring your organization to its knees. Sorry; that was just a small joke, but the irony is hard to avoid. I mean, we’re all looking for kind of the same thing, aren’t we: a chance to bring people together and get ahead, and maybe, just maybe to put together a great group of people and doing something really HUGE in life. The fact that we feel the need to state and restate the obvious is just a bit funny, don’t you agree? And that leads me to the purpose for which I write you today.

The purpose of my writing you is not simply to give you a good laugh at my frankness and cleverness, although I hope there’s that. Rather, I’m writing you to let you know that I think I have the skills you’re looking for to do the job you’ve outlined in your ad. But, moreover, I think I have the personality, the experience, and — let’s face it — the sheer determination that your organization needs to do great things. You and I both know that it’s the little things in people that make the big differences in an organization. That attention to detail. That enthusiasm that seems to come out of nowhere. That sense of ownership. I’d like to submit to you that I believe I have those little things that will help you succeed in your own aspirations.

I understand your needs as a team leader to have great people because I’ve had to put together my own project team in the classroom to build great software (ask me about that sometime). I have a sense of the weight of your responsibility to drive success because I spent seven years working for a disciplined, results-driven organization. I understand how our product will need to be positioned for customers — both from a marketing and a technology point of view — because I eat, sleep and breathe the web. I even have ideas about how your product will need to change in the next five years because I spend my free time reading the books, articles and blogs by the people who are building this stuff on the cutting edge.

So, here. Attached is my résumé — take a look and see if you agree that I just might have something to offer. If you like what you see, give me a call and we’ll chat. Meantime, thanks for your attention; I’m looking forward to a mutually profitable relationship in the near future.

Sincerely,
Ken

When Mike replied to my blog on the 21st, he said:

Thats just a really deep way of saying, ‘I have a job that makes me think.’

Er, well, actually it’s more than that. By saying that projects are journeys, I mean they are a means of going from one place to another. The skillset that I had before the TVC site was different from the skillset I have now. The things I know about our church are different. The way I approach working on the site now is different than when I started.

It’s also the same where I work. One particular project I’m working on now has to do with deploying a CRM tool to a sales organization. Once you get involved in enterprise-wide systems, you start to learn all sorts of things about the enterprise–both its people and its systems. I have learned a lot in the past several months on this project and, if all goes well, I will be able to look back several months from now and see what I’ve learned and accomplished and, perhaps more importantly, see how I can use those learnings on future ventures.

Mike included in his comment my remark, Systems design is both passive and active; its simultaneously something that you do and that happens to you. This highlights my point about the journey. When you embark on a project, it’s not immediately clear what information is known and what is unknown. It’s not clear what is to be built and with what reqiurements. It’s not clear where the budget is coming from. It’s not clear who will take ownership of the completed product. It’s not even clear whether or not the proposed idea is even going to work. This is an epistemological problem–how do you know what you know?–which is, I think, really unique to project management and delineates it from other work.

Jobs have a relatively constrained set of rules by which you play. These are usually understood well in advance (“I fold papers and stuff envelopes”) and determine the majority of your choices. Systems design is way different. There are constraints that go into systems design, but they are not all well known at the start and are learned along the way.

True, this does make me think, but stating that projects are journeys isn’t just a flowery way of saying so. :)

A project is just another job. You have nothing, or very little when it starts and a product at the end. It actually kinda bothers me that it is being thought of differently.

Actually, the difference between a job and a project is fairly well defined. The Wikipedia definition isn’t great (and I might just go change it myself after this blog), but a project is, essentially, the coordination of resources within a set of constraints (such as time and money) to accomplish a goal. That goal is inherently the creation of of something new that didn’t previously exist.

If I could perhaps rework the terminology a bit:

==

work
an ongoing process of doing what is necessary to run the business
e.g. turning on the lights, maintaining software, filing paperwork
project
a time-bound process of creating something new for the business
e.g. installing new light fixtures, designing a new software application, creating a new filing system
job
a role that may encompass work, projects, or a combination of both

==

So, for example, you could have a job that encompasses work (such as grading students’ papers) and projects (such as creating a marching band program). Make sense?

Work and projects are different in what they produce, so they need to be managed differently. Imagine you’re a widget-maker. You enter the office every day and sit down at your desk and crank out widgets–maybe 30 or 40 per day. This is work. Your knowledge of widget technology is fairly static and your focus for improvement is on output–perhaps your bonus is determined by the number of widgets you produce. This is how you manage work.

Perhaps your company wants to be the world leader in widget development and they’ve tasked you with inventing the next best widget. This is a project. What do you do? You set goals and meet with widget content-experts to get their feedback. You make plans to try out different widget designs. You go looking for money in the organization to develop your widget. A timeline is most likely given to you (and it’s most likely by freakin’ marketing) to have new widget development completed in six months. This is how you manage a project.

Now imagine yourself an employer. You have people on your payroll that do work and people that do projects. The people who do work keep the business running so you can make money to pay your bills. The people who do projects advance the business in ways that make new money–either by developing processes that create efficiencies (which results in savings), or by developing processes that may create new opportunities (which results in capital). For example, a business can undertake the project of launching an e-business portal (that term sounds so 1997), which results in sales in a new market that didn’t previously exist and therefore new money.

Now, you’re still that employer. Which kinds of employees are you going to be more excited about? Most likely, the project people–they’re the ones bringing in the new money to the business. This is why business are all gaga about project-based work, and why lots of people are getting involved with project management.

Gigs

  1. Wile away the best years of your life building a weblog and filling it with useful, interesting, relevant, topical, engaging content every day.
  2. ???
  3. Profit!

Mark Pilgrim, Dive Into XML

So true. Recent grumblings regarding my blog idleness are the result of this simple formula. Back when I was a student (and had free time), I ranted and raved about Pagerank and accessibility and usability. One would think that such histrionics would send our readership screaming from their bookmarks. On the contrary, some people read that and actually came under the impression that I knew what I was talking about, so I’ve been able to stack up a few web design and consulting gigs to pull in some extra Benjamins. I’ve found spending my free time building things I enjoy for profit to be a lot better than wiling my life away in front of the television. But then, aparently anything would be a lot better than wiling my life away in front of the television.

No announcements just yet, but the projects I’ve been involved in have been a lot of fun. For one project, the client came to me with a design already in mind. This turned out to be remarkably challenging because a number of his design influences came from Flash-based sites. Flash always reminds me of this part in Steve Krug’s web usability book, Don’t Make Me Think. In it, Steve is trying to convey to the reader the typical internal power struggle over the corporate home page at Generic Widget Company. He very cleverly–everything about this book is very clever, actually–sketches little thumbnails of each stakeholders’ impression of the ideal website. The marketing guy envisions columns of banner ads, the programming guy envisions an ugly (but very functional) form, the graphic design guy envisions a très minimaliste aesthetic wonder. But all the CEO envisions is one thing: “Pizzazz!!!”

Flash, with all of it’s swoopy eye-candy appeal, is pizzazz. But sensible site architecture will always, always, always trump the pizzazz factor. Sooner or later, someone will have to make a change to the site. Or design fads will change. Or Marketing will complain that the site isn’t drumming up enough business. Technologies built using web standards enable clients to cope with change; Flash does not. Ultimately, though, it’s The Google Argument (“what Google doesn’t know will hurt you”) that cinches the decsion between a standards- or Flash-based site–not because of Google per se, but because of what Google represents: what Jeffrey Zeldman calls the forward-compatibility of your website.

But then, using Google to argue for web standards and accessibility is so 2002. It’s far trendier to deconstruct blogs out of hand. It’s so much fun. Let’s try it:

Hi. I’m writing about how blogging has made me lots of money. Let me wow you with my aristocratic opinions about television. Did I mention that I’m doing web design? Google is great. Hey, blog deconstruction is fun! Let’s try it…

The best part of that game is that it never ends; it’s turtles all the way down.

Anyway. I’m also working on a web design consultation. This is great, because I get to work on my technical writing skills and not have the burden of doing any markup whatsoever. Not that I don’t like thinking in HTML, but consulting takes me one step closer to the project management career track that I’m aiming for. That, and it has the lovely ring of “getting paid for my opinions” to it. Sam Andreades introduced me to this concept in a sermon several months back (ironically, a sermon about being humble), and it sounded like a fantastic idea. I love to hear myself talk–so much so that I think others should have to pay to hear me talk, too.

Narcissistic tendencies notwithstanding, both of these projects have brought me back to why I love software in the first place: good software is about empowering people. If you write software, never ever forget this. If you use software, neglect of this principle is the essence of what makes you want to hurl your computer out the window. Writing good software should always be about enabling people to do new, cool stuff that they only previously could have imagined. I have a personal aspiration at work, “to be recognized as a creator and leader of insanely great technology.” The nod to Steve Jobs here is inevitable; when Apple is successful, it is because they have men and women who take this empowerment principle very seriously.

Some consultants run their businesses on the very opposite of this idea: the more the client is locked into a proprietary system to which they have exclusive knowledge rights, the more secure their employ. The payout on this principle, though, delivers diminishing returns and actually limits your skill set (read: makes you dumber) over time. Why spend your precious time (and your client’s precious money) building things you’ll have to change six to eight months from now? In the end, you spend too much time fixing stupid problems and adding marginally useful features. Things the client should be able to fix. Time that should be spent dreaming up new and interesting ways to empower people. Helping people accomplish great things that they were never able to do before is more than just good business, it’s also far more rewarding work.

Mozilla Changes Gears

There’s quite a buzz in the Mozilla community about an organization restructuring. This restructuring comes with the third modification of Mozilla’s roadmap.

Mozilla: Mozilla Development Roadmap. We have come a long way. We have achieved a Mozilla 1.0 milestone that satisfies the criteria put forth in the Mozilla 1.0 manifesto, giving the community and the wider world a high-quality release, and a stable branch for conservative development and derivative product releases. See the Mozilla Hall of Fame for a list of Mozilla-based projects and products that benefited from 1.0.

This is but a small section of the rich discussion of the Mozilla restructuring available at the site, which contains some exciting announcements. Among them:

* Phoenix is going to become Mozilla’s major browser development effort
* Thunderbird—a mail client similar to Phoenix’s agile application design—is going to become Mozilla’s major mail client development effort
* Aside from the migration towards these applications, much of the development effort will now focus on making Mozilla do what it does with a more streamlined codebase
* Advanced-user featuresets will be built as modular plugins—this is particularly good news if you’ve ever tried navigating the drop-down menus in Mozilla and got overwhelmed with too many options

…and there’s more interesting activities that aren’t explicitly constrained to the application end-user.

I’ve had a growing interest in Mozilla over the past year or so as I’ve encountered more educational experience in programming and project management but little ‘real world’ work experience. What’s cool about the project is that everything is out in the open for everyone to see. If you want to learn how to hack Mozilla, you can. If you’re interested in seeing the latest bugs in Phoenix, you can. If you want to discuss issues with the developers directly, you can. If you want to peruse code, you can. Even their development timeline is available. The Mozilla project offers, for the wannabe hacker, an opportunity to see real development efforts in action and, for the project manager, the opportunity to see what works and what doesn’t.

What’s more exciting, though, is that the Mozilla project seems to be undergoing a turning point similar to the one that Linux underwent a couple of years ago: the popularization and user-orientation of the project. Not only has the Mozilla project created a viable, standards-based choice for cross platform development (such as the much anticipated OpenMind project), but is now creating applications that are meaningful for the end user. My favorite of these is, of course, the Phoenix web browser. (Haven’t made Phoenix your primary web browser yet? Here’s a good list of reasons why you should.)

As Mark Pilgrim put it recently, In the future, there will be so much open source software available, programmers will be judged by how much they know about it and how well they can glue it together to build solutions. Looks like this year is going to be a pretty exciting jumpstart into that future.

One of the interesting (if tedious) responsibilities for my Senior Project class at NJIT is to discover, interpret, and choose a project management methodology. Having had no real prior experience in the theory of project management, this has been a real challenge to me: I feel like I’m desperately trying to claw my way up from the bottom of the learning curve. Read on for more.
View Full Article »

Open Source Project Management

Update: it’s no secret that I am using Basecamp for project management these days.

Basecamp project management and collaboration

The Linux desktop may not be ready for Joe User and his grandmother, but is it ready for the knowledge worker? This is a question I’ve somewhat accidentally been endeavoring to answer since the semester started. A lot of people go looking to prove Linux out when it comes to the desktop in a sort of anti-Microsoft methodology. My latest experimentation, though, wasn’t born out of a desire to prove Linux right or Microsoft wrong—it came out of an immediate need for tools to get my job done as project manager at school. While NJIT provides a lot of these programs for download through Microsoft’s Academic Alliance program, I wasn’t able to get a hold of them easily (the intranet site required that I authenticate three separate times, and still wouldn’t let me do it!). Read on to see just how Linux is performing in these areas.

View Full Article »

Bad Day at Work

My friend Roger managed to articulate my day in a nutshell (I guess this Friday’s been a rough one for everyone):

     ”Roger, [so-and-so] was looking for you.”

     Roger: “Yeah…I think I’m just going to start handing out darts.”

Powered by WordPress and Motion by 85ideas.