This week I had to wade into the depths of a Large Project; well, actually a component of a Large Project, that was struggling a bit to find a path through the forest. Not my first time, certainly not my last, and (believe it or not) usually a pretty good time! <aside> Ok, by "large" I mean "amazingly high profile, visible to Upper Management, involving Lots of Talented, Busy People" </aside> <aside> Ok, by "Talented" I mean "terrific at their…
Here's an interesting phenomenon I've encountered before ... When analyzing a specific section of a business, people seem to naturally focus attention and conversation on the top two or three customers/products/vendors that together represent (say) 20% of the revenues/costs/contracts. Our objective is to look at the data and identify opportunities (increase revenues, cut COGS, aggregate contracts); unfortunately, processing the data for these customers/products/vendors is currently a 100% manual task. Of course; this is why there is apparently so much "opportunity"…
I remember in the late 90's, seeing many examples of the little train of wedgies that folks used to characterize their business processes: I've used them myself (some of the above samples are mine, I'm comfortable in admitting it) - of course, I typically don't make this stuff up, I adapt from other examples, like everyone else. As I searched for a reasonable picture / schematic / "framework" for a "supply chain", I stumbled across what I believe to be…
I've been IM'g in a work atmosphere for over a year now, with internal and external folks, and still actively networking for tech info, support, etc. That peer group has a fairly well-defined set of etiquette, jargon, and style. In my new company, we are rolling out enterprise IM, and for most folks (including IT!), this is a "foreign language". (I'm "jpm1234" in the conversations below ...) Challenge #1: I think faster than I type, so I get a bit…
Why do some folks insist on answering questions with questions? Or, answering questions with roadblocks? It's not surprising when you hear IT complain about their inability to connect with the business, of not being included, etc. - and then demonstrate a style of investigation / requirements gathering / support / feedback that is a bit antagonistic. Business: How long would it take you to do X? IT: Why X? Why not Y? ... or IT: Why X? What are the…
As I sit in meetings, I find myself thinking through "process" of what we are doing at this moment, as much as I think about what the meeting is about. Then I am writing these short notes to myself for future blog items. Good? Bad? Psychotic? It makes me wish for easier tools to convert notes to complete text - but look at this chicken scratch ... I like these pseudo-postings for process think because I am lazy at heart,…
Had a good conversation with a vendor last week. They were looking to increase their business with us, no surprise there, but the rep was actually a bit cynical (in a nice way), and (probably wisely) asked directly what the chances were that we could actually get Project X off the ground? I've seen these great ideas start, but then some manager complains that they have no budget for this kind of thing. In retrospect, it is almost a rude…
I had a fun time this week proposing an open source alternative for an aging component of our EAI infrastructure. The reaction was so classic - the instant some IT folks saw the words "open source" in large type on the piece of paper, they smiled, crossed their arms, and tut-tutted the idea away. Oh, I heard all the classic shoot-down arguments ... "... critical piece of our day to day business transactions ..." "... I rarely need to call,…
A classic problem for many project-oriented organizations (IT, R&D, Engineering, Operations) ... how can resource prioritization be simplified, yet repeatable? It's a fairly involved topic, but a common approach is to group projects into a workable number of "chunks" ... we'll use the term Initiatives. How will this help? Challenge: Clarify the team's priorities, alignment, and resource levels - without going into the details The CEO asks a question – what Projects are on the to-do list for IT? [Do…
It's difficult for many to understand how open source applies in the business world. Most folks get trapped in the mindset of software as product, yet many folks have built businesses based on Open Source - usually by giving away the software / algorithms, but selling implementation services. The Trolltech story is another (typical) twist - free software for non-commercial use, but licensing the stuff to corporations. Why would the latter work? Because of the other difficulty business has with…