| IBM Reorganizes Itself to Reach Midmarket Customers |
|
|
|
| Analysis - Analysis of News Events | |
| Written by Lee Kroon | |
| Sunday, 20 January 2008 | |
|
While IBM's latest management moves deserve kudos, there is something else that the company must do to revive its flagging systems sales.
If you have not heard from your favorite IBM representative lately, there's a good reason. Over the last several weeks, Big Blue has been putting itself and its employees through one of the biggest internal reorganizations in its long history. The new management structure will have far-reaching implications for how IBM works with small and midsize businesses (SMBs) in general and System i customers in particular.
In separate but closely related actions, IBM took apart two of its biggest organizations and reassembled them in dramatically different ways. The first shoe dropped on January 3 when Bill Zeitler, Senior VP for the Systems and Technology Group (STG), announced a top-to-bottom restructuring of his worldwide team. For years, STG has been organized into product groups such as the System i and System x Divisions. These groups operated in relative isolation from each other, with each division having its own sales specialists and support teams clear down to the territory level. This led to customers being called upon by multiple STG teams and IBM Business Partners, each with a proposal for its designated system. Such situations are frustrating for SMBs as most of them prefer integrated IT solutions to bewildering hardware options.
To address this problem, IBM has created four new STG divisions that focus on discrete customer segments instead of hardware products. The Enterprise Systems Division serves large companies. The Business Systems Division focuses on companies with less than 1,000 employees. The Industry Systems Division caters to the special needs of specific industries such as retail, healthcare, and life sciences. The Microelectronics Division works with IBM's OEM component customers. Each division has its own General Manager (GM) who reports to Zeitler. These GMs are responsible for satisfying the needs of their customer segment. They are also responsible for all marketing and sales campaigns in their segments as well as all sales goals.
While STG still has product-focused divisions and GMs, their names and roles have undergone significant change. The Mainframe Division now manages the System z while the Power Systems Division is in charge of System i, System p, and Linux systems running on POWER processors. The Modular Systems Division owns the System x and BladeCenter portfolios, leaving the Storage Division with disk and tape devices. The GMs of these "platform divisions" report to Zeitler just like their "client division" counterparts, but their responsibilities are different. The platform GMs are to focus on making their products competitive and ensuring that they are complete and integrated "solution stacks." They are also responsible for providing technical support to the sales teams that now report to the client divisions rather than to them.
Next Stop: A Field Force MakeoverSpeaking of the sales teams, big changes are taking place to them as well. Historically, each of IBM's roughly 300 sales territories has been staffed by sales and support employees who specialize in an STG product. While these specialists will remain in the field, they will now be dedicated to specific customer accounts and will report to the Enterprise, Business, or Industry Systems Divisions. They will also represent STG's entire product portfolio to their accounts, not just their area of specialization.
To push this client-centric concept further, IBM announced on January 8 that it is reorganizing its Small and Midsize Business Group, the division that manages the SMB sales force. The action splits the group into two teams. One team will focus on larger midsize companies that have the potential to become enterprise customers, while the other will focus on smaller "genuine" midmarket companies. By dedicating resources to this second set of companies, IBM is aiming to avoid the common situation where a big sales opportunity in a larger company soaks up most of the sales resources in a territory. This has led to many companies (including System i customers) being ignored by IBM.
To appeal to midsize businesses, IBM will also boost its marketing budget for reaching these firms to $100 million in 2008. That's a 25 percent increase over what the computer giant spent in 2007. Much of this money will fund demand-generation efforts while some will flow to IBM Business Partners in the form of sales incentives. IBM will also designate employees in each territory as "midmarket representatives" and give them sales quotas.
Another Management Shuffle...Should We Care?To many people, reading about an IBM reorganization is as exciting as watching scrap metal rusting. Nevertheless, don't dismiss what's happening inside Big Blue as irrelevant. Here's a short list of how the reorganization could affect System i customers. •· You may soon find that some of the IBMers you work with have been reassigned elsewhere or that new people are calling on you. That could change how you do business with IBM, especially if you rely on certain people for help. •· Over time, you could find yourself working with a more stable team of IBMers. By dedicating specific staff to specific accounts, IBM is working to present a "single face" to its SMB customers. That could make it easier for smaller companies to do business with IBM. •· You may find it easier to get IBM's attention when you have a need. This could especially be the case for smaller companies in sales territories that have traditionally been dominated by larger enterprises. •· You should see more IBM marketing aimed at companies like yours. However, don't count on a System i ad blitz, because it isn't in the cards. Importantly for System i customers, the reorganization reverses a decision that IBM made last July to split management of the System i between the POWER Systems and Business Systems Division (BSD). Effective immediately, all System i models are managed by the POWER Systems Division, which is managed by Ross Mauri. That said, BSD will still be responsible for packaging and selling STG products for the SMB market. Those packages will include all System i models as well as relevant products from the other platform divisions. As I mentioned in my last article, I expect BSD to make big announcements this year about cross-brand offerings for SMBs.
While the reorganization could improve how IBM communicates with SMBs, it does little to address another problem: the bureaucracy that has taken hold inside much of IBM. Indeed, the reorganization may fan the bureaucratic flames by increasing the number of divisions and GMs in STG. That could strengthen what has, in my opinion, become a "matrix management culture" in which too many managers avoid taking bold actions for fear that one of the multiple executives they report to will oppose them.
I shudder to think what will happen to the System i if timidity levels increase inside IBM in general and STG in particular. If there is one STG product that requires bold, independent action to thrive, it is the System i. Unlike IBM's other SMB servers, which often look like what everyone else is selling, the System i is a server that stands apart from the crowd. To sell it effectively, you need people with an unflinching belief that different is often better.
Sadly, such maverick spirits have become increasingly harder to find inside IBM. That is unfortunate because many of IBM's greatest product successes--the venerable System/360, the IBM PC, and the AS/400--were developed by freethinkers who took issue with their company's prevailing wisdom. While I hate to say it, today's IBM may have lost the courage to listen to the mavericks within its ranks. In my opinion, the latest reorganization will do little to change the situation.
In short, I applaud IBM's efforts to reorganize itself around the needs of its customers. I believe it will make it easier for the company to gain the attention of SMB organizations and improve how it communicates with them. However, unless IBM has something powerful, relevant, and different to say to those organizations, it will not hold their attention or win them over from competitors. If IBM wants to leverage its reorganization, it needs to do something even bigger and more disruptive. It needs to re-create a corporate culture that rewards bold, independent thinking...the kind of thinking that brought the AS/400 into being.
This year marks the 20th anniversary of the birth of the AS/400. What better occasion could there be for IBM to rediscover its inner maverick? |
|
|
Last Updated ( Friday, 18 January 2008 ) |
|
| efnkay |
Re:IBM Reorganizes Itself to Reach Midmarket Customers
Jan 24 2008 05:23:59 Just to offer that RPG/ILE is the front-runner but aren't there also C and Cobol programmers out there on i5's, PL1 guys maybe?
|
#121683 |
| H.Boldt |
Re:IBM Reorganizes Itself to Reach Midmarket Custo
Jan 23 2008 23:43:33 Tom Daly wrote:
Setting aside these other issues and sticking just to the topic of the language, what would you like to see for RPG? IIRC OO is not on your hit parade. Off the top of my head, here are a few things: First, complete free-form syntax. Come on guys, it's 2008! The fixed-form syntax alone is sufficient to rank RPG as a relic of the 1960's, and not a modern programming tool. Next, I'd like to see a new implementation of character strings. The current CHAR VARYING is mired in performance problems. CHAR VARYING return values, although having a nice syntax, involve the copying of way too many bytes. Likewise, other character operations like catenation require too much movement of bytes to and from temps. RPG should have a new STRING type where a pointer addresses the string data in a string pool. Returning strings from procedures would involve returning just a pointer, not thousands of bytes. The STRING type should also handle all Unicode issues, which are also currently poorly addressed. Third, pointers should be strongly typed. Many RPG programmers seem unwilling to use a more appropriate language like C for systems programming. In C, the strong pointer typing can help programmers find potential problems at the compile stage. Without strong typing, debugging pointer type mismatches at run-time can be very difficult and time-consuming. Fourth, there should be some syntax for parameter polymorphism on procedure calls. That is, procedure call "foo(charvar)" would call one procedure and "foo(numvar)" would call another. After that, there are lots of easy little things that could be done, such as %LOOKUP on array DS based on subfield, or SORT of array DS keyed on a subfield. Array element initialization should be easier. One problem with this is that for some of these things, the old functionality still needs to be supported. This can be good or bad. For example, I know from experience that if you have the ability to bypass strong pointer type checking, you will. This results in a language that offers multiple different ways to achieve some coding problem depending on release. Other languages take a much different approach to R->R compatibility. Consider Perl 6 and Python 3: These languages are different than their predecessors. The owners of these languages have weighed the pros and cons, and made the decision to deprecate certain older language features. (I believe Perl 6 tries to recognize the older syntax, while the less drastic Python 3 offers a conversion tool.) Doing that for RPG would be very difficult since IBM's customers have come to expect strict R->R compatibility. Cheers! Hans |
#121681 |
| Tom Daly |
Re:IBM Reorganizes Itself to Reach Midmarket Custo
Jan 23 2008 02:58:17 Setting aside these other issues and sticking just to the topic of the language, what would you like to see for RPG? IIRC OO is not on your hit parade. Namespaces? Aspects?
Tom D. |
#121670 |
| H.Boldt |
Re:IBM Reorganizes Itself to Reach Midmarket Custo
Jan 23 2008 01:47:09 Tom Daly wrote:
Realisticly, what features do you think would make RPG more modern, more productive, and cool? What would make it futuristic? _That_ would be cool! What's it lacking? In your wildest dreams, what would you like to see for RPG? ... Personally, I think we're way beyond that. I don't think putting half-dozen more developers (or more) on enhancing the language is going to make any difference in the long run. Besides, if you change the language too much at any one time, programmers complain about the training needed, or that they can't use the enhancements since they won't get to the current release for another 3 years, or the enhancements should have been done differently, or whatever. Let me offer another angle on my analysis: The cheaper the System i gets in comparison to other systems, the more cost-effective it becomes to run interpreted OO languages on the system. That is, the more it becomes a commodity-priced solution, the less important RPG will be to the system. The less important RPG is, the less the need for the i5/OS and System i. I know from direct personal experience how many companies are hiring System i programmers these days. In the GTA east area where I live, over the past 5 months there has been a total of one company hiring, and that one is in yet another declining business: cutting pre-recorded CD's and DVD's. I would be much more confident in the System i's future if there were more positions available. The System i will survive for a while yet on the strength of its existing SMB applications. But over time, these will either drift over to commodity systems, or will get more competition from commodity-based solutions. If you have a different take on the situation, let's hear it. I know there are others out there who see a brighter future. Cheers! Hans |
#121669 |
| Tom Daly |
Re:IBM Reorganizes Itself to Reach Midmarket Customers
Jan 22 2008 08:58:46 Hans,
Realisticly, what features do you think would make RPG more modern, more productive, and cool? What would make it futuristic? _That_ would be cool! What's it lacking? In your wildest dreams, what would you like to see for RPG? I'd like to think RPG has a good future too, and you're certainly in a position to have some interesting insights. Hopefully this will spark a little life into this forum! Tom D. |
#121667 |
| H.Boldt |
IBM Reorganizes Itself to Reach Midmarket Customers
Jan 22 2008 01:38:34 This thread discusses the Content article: IBM Reorganizes Itself to Reach Midmarket Customers
I'm sure I'll get a lot of disagreements, but here are my thoughts on this subject: First, in response to Lee's comment "While I hate to say it, today's IBM may have lost the courage to listen to the mavericks within its ranks.": Considering the reorgs and "staffing actions" that have gone on in the past five years, I wonder how many mavericks are left at all. Second, with respect to what should be done with the System i, I'm not sure what can be done. Today's situation in very different than when the AS/400 was developed. Compare the System i with the System p. The only real difference between the two is that one can run legacy RPG apps and is more expensive. In other words, pushing the System i involves selling RPG as a modern development platform. IBM basically has to find a way to make RPG more attractive than other alternatives which are either cheaper or provide significant productivity advantages or are simply more "cool". As someone who spent years working on RPG compilers at IBM, I'd like to think RPG has a good future. But we have to be realistic. Cheers! Hans |
#121666 |





