Showing posts with label Career. Show all posts
Showing posts with label Career. Show all posts

Monday, April 14, 2008

An Unexpected Turn at Management

I have not been nearly as successful at integrating blogging and podcasting back into my life as I wanted after my unreal, fantasy assignment in China ended at the end of October 2007. After the holidays and after some procrastination on my part, I was hit with a reorganization at work. Suddenly I was asked to be a first line manager.

For some people this would have been an exciting event and cause for celebration. But for me it was cause for pause. In some ways I had made a career out of not becoming a manager, a pure sales person, or a project manager. I had managed to advance to a pretty high level on mostly my technical merits, successful projects, and some happy clients who kept signing up for more services based on that success. I was comfortable in a career path that would hopefully get me at least one more promotion some day (soon I hope) to what IBM calls a "Distinguished Engineer." I was to be a mentor but not a real manager.

Now I was asked to officially take over the care and feeding of 14 specialists and architects. Something inside told me that I should say "yes" and give it my best shot. I still want to be a Distinguished Engineer but I think now is the time to grow some other skills which may prove valuable later. In the past, when something unexpected happened in my career it usually turned out to be for the best after all. Visit my other blog if you're curious about my outlook on such things.

Copyright © 2008 by Philip Hartman - All Rights Reserved

The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Monday, February 11, 2008

International Conference on Global Software Engineering

If you have been a regular reader of my blog, you know that globalization is one of my favorite topics of discussion. Therefore, I would like to draw your attention to the International Conference on Global Software Engineering which will be held August 17-20, 2008 in Bangalore, India. (Recently renamed Bangaluru.) The event is sponsored by the IEEE Computer Society.

Please note that if you have some thoughts to share, there is still time to submit a paper. The deadline for abstracts is Feb 21, 2008 and the deadline for papers is Feb 28, 2008.

Yours truly is a member of the Program Committee for the event. However, that doesn’t mean I automatically get to attend. I still have pay the registration fee and pay to get myself there… or convince my employer of the wisdom of spending their money to send me. I had the good fortune to visit my team in Bangalore and interview a few programmers for positions back in the fall of 2004 and I would certainly enjoy a return trip for the conference. I would be curious have any of you (my readers) had success at securing funding for travel to this kind of thing? If so, I’d love to hear how you justified the expense to your employer.

Copyright © 2008 by Philip Hartman - All Rights Reserved

The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Sunday, February 10, 2008

Do You Use a Dash?

This may be a silly thing, but when you write your job title, do you write it as "I/T Architect" or "IT Architect" ?

I got used to using the slash several years ago. I think that is what I saw most often inside IBM where I work.

However, now it seems that I am seeing the title written without the slash. I noticed that the Open Group certification program uses no slash. (See the Master Certified IT Architect logo on the right side of my blog.)

I'm tempted to abandon the slash. What do you think? Which do you use? Which do you like better?




Copyright © 2008 by Philip Hartman - All Rights Reserved




The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Wednesday, December 19, 2007

Now Podcasting, Too !

One of the things which I learned in China is that many of the young, educated, professional Chinese view having good English language skills as a prerequisite to many of the top jobs in China. Apparently, the best jobs in China all require regular interaction with foreigners like me. I found they were a lot more interested in me helping them with their English than in helping me learn Chinese.

For some reason, I found that many found my voice, cadence, and diction easier to understand than most. (Maybe they were just trying to be nice to me?) Being from Tennessee in the American South, I mentioned this to an American from South Carolina that I met in Beijing. He laughed and told me that "the Chinese love Southerners because we talk slow." Whatever the reason, I took an interest in teaching English and came up with the idea of using a podcast with corresponding transcript to assist my new friends with pronunciation even when I am not around.
Off topic for this blog... but for anyone who might be interested I even got to teach English in a Chinese government-registered church. See My Chinese Church Away from Home.

I decided to start a podcast equivalent to this blog at http://artsciita.podbean.com/. If English is not your native language, I hope you will check it out. This is something of an experiment so if you try it and like it, you had better let me know. It is a little extra work on me and I might lose interest if nobody seems to be paying attention. Here's an online MP3 player with links to share our subscribe to the RSS feed. I went back and added voice for the most popular posts and a few of my personal favorites.

Copyright © 2007 by Philip Hartman - All Rights Reserved


The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Back to the Real World After China

About 6 weeks ago, I completed one of the most challenging 10 months of my entire 26+ year career. I helped create the Enterprise Service Bus for a major Chinese company and during that time I made six trips to China and spent a total of 4.5 months there. I joked with friends that I did not live in the "real world" anymore because I would have never believed that anyone would actually pay me to work in China for so long. I did, however, learn a lot about globally distributed teams, ESB's, SOA, and the culture clash of trying to make people from China, the US, Canada, and India all work together.

In particular, my job was to help integrate their website with 3rd party service providers and their SAP back end. My resume is now full of references to XML, web services, canonical data modeling (XML schemas), WebSphere Message Broker, and WebSphere Process Server.

It was a heady time but I must confess I'm glad its over. It has taken me several weeks to get back into the groove and sit down and take some time to blog again.

Copyright © 2007 by Philip Hartman - All Rights Reserved

The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Wednesday, May 09, 2007

The Global Lifestyle Time Challenge

I had a subtle career milestone today. Today I became fully aware that I was now "Global" ... with a capital "G" I think.

At about 6:30 am Central time I checked email at home before leaving for the airport. I saw an email from a business leader in the UK which set off alarms in my head that an important business decision my client needed to make was not being addressed. Knowing that a politically important deadline is approaching, I fired off a "this is a big issue!" email designed to alarm my readers that something important was not happening.

About 8 am Central time today I was waiting for a flight at the airport and my cell phone went off. It was that same business leader in the UK who took notice of my alarm. I don't know about you, but I don't get cell phone calls from people I've never met from other countries every day.

Shortly after arriving at my destination on the East Coast of the US, I scheduled a web meeting for tomorrow morning between people in Baltimore, Raleigh, California, and Beijing.

Later I was on a call between the US and Canada talking about interfaces to a system in China.

Still later I discussed architecture diagrams showing system components in Rochester (NY), Boulder, Dallas, Tulsa, Phoenix, Hong Kong, Beijing, and Toronto. I tried to figure out if the component in Hong Kong was really necessary. Could it be co-located with the rest of the stuff in Beijing?

I ate a hurried dinner of Tandoori Takki with two co-workers. One is a Norwegian citizen born in China but holding an American green card and the other was born in India but has been working in the US for a while. My history is boring compared to theirs.

Five minutes after checking into my hotel, I joined a conference call between the US and China but the co-worker from China didn't make the call. My co-worker later came online in China on instant messenger later and I pinged him about the call he missed. It turned out he was double booked for that timeslot. Heavy sigh. When are we going to solve time zone issues for calendars? I made sure he had the information for the web meeting in 9 hours.

This globalization thing isn't all its cracked up to be. Exactly when is it I am supposed to have some calm moments to think? When is it I am supposed to get more exercize like my doctor told me? Will the guy in California get up to make the web meeting at 6 am his time? Did I even have a right to call a web meeting that required someone to be there at 6 am? Will the guy in Beijing who has to join at 9 pm his time have a decent Internet connection? Did I have a choice on the time given that the guy we want to talk to was available then and it was a comfortable 9 am for him? Will my flight home on Friday be on time so I can make my daughter's piano recital? How early do I set my alarm clock for tomorrow? Early enough to hit the hotel treadmill or late enough to get another hour of sleep?

I have another trip to China coming up in two weeks. It is still fun for now. I can see how this could get old. I would love to hear how my readers in similar situations are handling the demanding hours, encroachment upon personal time, cultural differences, etc.

FYI, globalization has been a frequent topic of mine. You might take a look at some previous posts such as:


(Dec 2007) English not your native language? I've begun making podcasts of popular posts and they are available at http://artsciita.podbean.com/. Listen online at that URL, with the MP3 player below, or subscribe to the podcast using the RSS feed and listen with your favorite MP3 player.

Copyright © 2007 by Philip Hartman - All Rights Reserved

The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Sunday, April 29, 2007

I'd Rather Be Lucky than Good

This isn't my usual type of post because it talks not about concepts or competence but about a stroke of unusually good professional luck.


I was one of 4700 IBMers attending the Technical Leadership Exchange in Anaheim, California. I had just gotten a new assignment to create the canonical data model for my client's new enterprise service bus (ESB). I think of this as the superset of all the many possible data attributes of the major business objects that flow across the ESB. Examples would include purchase order, order acknowledgement, invoice, advance shipping notice, and more. The back end system for all of these transactions is SAP.


There was some training on Sunday before the conference started on Monday. At dinner Sunday night I sat down at a table of strangers and made some IBM smalltalk with my new acquaintances. A few minutes later some other guys sat down. The guy who sat to my immediate left asked me who I was, where I was from, what I was doing, etc.

When I mentioned I was working on a project to create a canonical data model for an ESB, he casually told me "Oh, I've been working on IBM's canonical data model for IBM's ESB for two years. I'm the lead architect." At this point I just about fell out of my chair. I could not believe my good fortune.


I told him I would pick up his dry cleaning and wash his car if he'd tell me everything he knew about canonical data models. He laughed and offered to help me.


To make a long story short, he wound up showing me the canonical data model for IBM's own ESB and pointed me to where I could download XML schemas off the IBM intranet. Incidentally, IBM uses SAP for many of its back end functions. One valuable tidbit of information included was a spreadsheet linking attributes in the canonical form with specific SAP IDOC segments and fields.


In the consulting business we call this "intellectual capital" and wonderful intellectual capital it is. Obviously, this has really jumpstarted my work. I wish I could say that I was really good but in this case I must confess being really lucky (or have I been living right?... that's another discussion).


He never did make me wash his car either. As we said playing basketball after someone said we were just lucky to make a difficult shot. Luck counts!

Friday, April 20, 2007

Word from the China Front

I had the good fortune to make my second trip to visit my client in Beijing, China. My trip was extended twice and I wound up staying three and a half weeks.

  • The reason my trip got extended was that one of my team's biggest recommendations related to eCommerce was rejected by the client as too expensive and taking too long. Heavy sigh. A worthy competitor has been introduced into the overall solution as a result.
  • I got to observe an interesting phenomenon. When an army of English speaking people fly to China to conduct meetings in English with Chinese I/T staff, the English speakers tend to dominate the discussion while everyone is in the room. The Chinese are generally soft-spoken and before they can mentally translate from English to Chinese, the English speakers move on to the next point. The Chinese are too polite to interrupt and say "you're going too fast." Therefore, the English speakers think there is a consensus only to discover objections later that never got expressed during the meeting.
  • I joined the team tasked with creating an Enterprise Service Bus (ESB) for the client. This ESB must span from North America to China. I think it qualifies as the "Brokered ESB Deployment Pattern" as described in my earlier post ESB Patterns that "Click".
  • I've been learning more about SAP and integrating SAP to other systems.
  • On a personal level unrelated to I/T Architecture, I got to have dinner with a member of Communist Party, to be amazed yet again at the incredible changes taking place in Chinese society, to visit the Summer Palace, to visit the Lama Temple, and take a bicycle rickshaw ride thru an old Beijing hutong. I got really tired of Kung Pao Chicken too.

Me at the Summer Palace in March 2007.

The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Friday, February 23, 2007

When do You Leave a Good Job?

It has been an embarrassingly long time since I’ve posted but I recently made a huge career change and I’ve been pretty busy. I’m afraid blogging dropped off my radar for several weeks. At least it was huge for me. As a consultant, I could change projects and clients without changing employer. Not everyone is that lucky.

Here’s a little history. I was encouraged by my management back in the fall to leave my comfort zone and take on bigger challenges. I think the handwriting was on the wall that I was as high as I could go in the organization if I stayed put. At first it looked like I might become what we call an “Associate Partner” in IBM Global Business Services and take on more of a marketing role. Instead, I wound up taking on an Enterprise Architect role in a truly global project.


Me at the Temple of Heaven, Beijing, China

I did indeed raise my hand and say “Yes” I will leave the position where I was happy, effective, and comfortable. I will leave the position where I got to sleep in my own bed every night and “jump into the frying pan.”



National Software Technology Park - Beijing, China

I knew I wouldn’t be bored. But would I be happy?

This whole experience had led me to think a lot about the question “When is the right time to leave a good job?” This is not an easy question. I think it strikes at the heart of our professional identity. I had to do a lot of soul searching about my priorities. I had to face questions like:

  • What is really important to me?
  • Am I content to stay where I am and continue to do what I’m doing?
  • What is the cost career-wise of staying put?
  • Is it better to leave now on my own terms rather than wait for some executive to make the decision for me by phasing out the position before I’m ready to leave?
  • Is it really possible in today’s global economy to have work-life balance?
  • Is it really possible to “work smarter not harder”?
  • Are there intangible benefits to making a change outside of my career?


If you look at my situation purely from a career point of view, I stayed in my previous position too long. Four years with one client on one major project using technology picked 3 or 4 years ago is too long for a technology professional. There were, however, other considerations such as the whole work-life balance issue. For me the decision to make a change came down these points:

  • I was getting a little bored because I’d been doing almost the same thing for four years.
  • I don’t know if it is healthy ambition or vanity, but I did find myself wanting the professional recognition and reward that came with a bigger, more visible project.
  • I think it is better to get out in front of large trends like globalization on my own terms rather try to hold onto what I’ve got and take the chance it might taken from me before I’m ready. A client once told me “There is an on-coming train coming. I can either put up my hand and try to stop it (and get run over) or try to get on board as the engineer.”
  • Biggest of all for me – the intangible benefits outside of my career. (If you’re brave enough to explore the spiritual side of leaving your comfort zone, click here.)

I’d love to hear what you think about leaving a good position. Have you ever done it? Did you regret it? Or did you never look back?

In case you're wondering how it is going... I'm working harder and working longer hours but I'm having a ball! So for now... it is good!

Click here if you are interested in my commentary and pictures about my recent travels to China. Still more pictures on flickr. Don’t forget Toronto.


Copyright © 2007 by Philip Hartman - All Rights Reserved


The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Tuesday, December 12, 2006

Fortune Favors the Prepared Mind

I'm not finished yet, but I can already tell that The World is Flat [Updated and Expanded]: A Brief History of the Twenty-first Century is going to be one of those books which is going to havea great impact on my professional life. There is so much truth (I don't have to like the truth) in the information presented, I was motivated to shoot an email to almost everyone in my email address book to recommend the book to them as a way to prepare for the impact of globalization on their life and careers.

The email had "Fortune Favors the Prepared Mind" as the subject line and read as follows:

A friend of mine recommended The World is Flat [Updated and Expanded]: A Brief History of the Twenty-first Century to me as a great book on the impact of globalization. I'm only about 20% done with it (the audio version) but I think there is a lot of good material on outsourcing, offshoring, India, China, etc. which I believe would benefit each of you as you think the future and the kinds of opportunities we all probably need to prepare for.

See also some great quotes from the book at www.wikiquote.org.

Some samples:

Every morning in Africa, a gazelle wakes up.
It knows it must run faster than the fastest lion or it will be killed.
Every morning a lion wakes up.
It knows it must outrun the slowest gazelle or it will starve to death.
It doesn’t matter whether you are a lion or a gazelle.
When the sun comes up, you better start running.
-African proverb

• In the pathbreaking 1989 essay, “Computer and Dynamo: the Modern Productivity Paradox in a Not-Too Distant Mirror,” the economic historian Paul A. David explained such a lag by pointing to a historical precedent. He noted that while the lightbulb was invented in 1879, it took several decades for electrification to kick in and have a big economic and productivity impact. Why? Because it was not enough just to install electric motors and scrap the old technology – steam engines. The whole way of doing manufacturing had to be reconfigured. In the case of electricity, David pointed out, the key breakthrough was in how buildings, and assembly lines, were designed and managed. Factories in the steam age tended to be heavy, costly multistory buildings designed to brace the weighty belts and other big transmission devices needed to drive steam-powered systems. Once small, powerful electric motors were introduced, everyone hoped for a quick productivity boost. It took time, though. To get all the savings, you needed to redesign enough buildings with small electric motors powering machines of all sizes. Only when there was a critical mass of experienced factory architects and electrical engineers and managers, who understood the complementarities among the production line, did electrification really deliver the productivity breakthrough in manufacturing, David wrote.

Bill Gates: 30 years ago, if you had a choice between being born a genius on the outskirts of Bombay or Shanghai or being born an average person in Poughkeepsie, you would take Poughkeepsie, because your chances of thriving and living a decent life there, even with average talent, were much greater. But as the world has gone flat, and so many people can plug and play from anywhere, natural talent has started to trump geography.

• America integrated a broken Europe and Japan into the global economy after World War II, with both Europe and Japan every year upgrading their manufacturing, knowledge, and service skills, often importing and sometimes stealing ideas and equipment from the US, just as America did from Britain in the late 1770s. Yet in the sixty years since World War II, our standard of living has increased every decade, and our unemployment rate – even with all the outcry about outsourcing – stands at only a little above 5 percent, roughly half that of the most developed countries in Western Europe.

• By automating these jobs, it enables companies to save money and free up talented brainpower from relatively mundane tasks to start new businesses in other areas. You should be afraid of free markets only if you believe that you will never need new medicines, new work flow software, new industries, new forms of entertainment, new coffeehouses.

• It takes a leap of faith, based on economics, to say there will be new things to do. But there always have been new jobs to do, and there is no fundamental reason to believe the future will be different. Some 150 years ago, 90 percent of American worked in agriculture and related fields. Today, it’s only 3 or 4 percent. What if the government had decided to protect and subsidize all those agricultural jobs and not embrace industrialization and then computerization? Would America as a whole really be better off today? Hardly.

• Well, here’s the truth that no one wanted to tell you: The world has been flattened. As a result of the triple convergence, global collaboration and competition – between individuals and individuals, companies and individuals, companies and companies, and companies and customers – have been made cheaper, easier, more friction-free, and more productive for more people from more corners of the earth than at any time in the history of the world.

• The sense that our kids have to be swaddled in cotton wool so that nothing bad or disappointing or stressful ever happens to them at school is, quite simply, a growing cancer on American society.

• In China today, Bill Gates is Britney Spears. In America today, Britney Spears is Britney Spears – and that is our problem.

• As exciting and as visible as the flat Indian high-tech sector is, have no illusions: It accounts for 0.2 percent of employment in India. Add those Indians involved in manufacturing for export, and you get a total of 2 percent of the employment in India.

• Immigrants are always hungry and they don’t have a backup plan. Young Chinese, Indians, and Poles are not racing us to the bottom. They are racing us to the top. They do not want to work for us; they don’t even want to be us. They want to dominate us.

• The best companies outsource to win, not to shrink. They outsource to innovate faster and more cheaply in order to grow larger, gain market share, and hire more and different specialists – not to save money by firing more people. (p. 360)

• The business organization consultant Michael Hummer once remarked, “One thing that tells me a company is in trouble is when they tell me how good they were in the past. Same with countries. You don’t want to forget your identity. I am glad you were great in the 14th century, but that was then and this is now. When memories exceed dreams, the end is near. The hallmark of a truly successful organization is the willingness to abandon what made it successful and start fresh.

• People don’t change when you tell them there is a better option. They change when they conclude that they have no other option.

• Louis Pasteur said it a long time ago: “Fortune favors the prepared mind.”



The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Monday, November 27, 2006

Overtime Pay for I/T Architects?

I didn't even know this was going on until this morning, but apparently several high-tech companies including IBM, Siebel, and Computer Sciences Corp. have settled class action lawsuits regarding overtime pay for technology workers.
"International Business Machines Corp. settled a federal class-action lawsuit Wednesday, agreeing to pay a total of $65 million to 32,000 technology workers who claimed the company illegally withheld overtime pay....The case involved workers classified as "Technical Services Professional and Information Technology Specialists." IBM considered them highly skilled professionals exempt from overtime laws detailed in the Fair Labor Standards Act and California labor laws....Software maker Siebel Systems Inc. settled a class action suit by more than 800 workers earlier this month. The workers, who had job titles such as "software engineer" and "senior software engineer," will receive a total of $27.5 million....Last year, El Segundo-based Computer Sciences Corp. settled an overtime class-action suit by 30,000 employees for $24 million. "
For more complete details, see IBM Settles Overtime Lawsuit for $65M.

I don't plan on spending the money until I see it in my bank account. :-)

Copyright © 2006 by Philip Hartman - All Rights Reserved

The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Sunday, October 08, 2006

College Hiring

I present this little bit of anecdotal evidence that employment prospects for I/T professionals here in the USA are bright. I am making my first college recruiting trip! I will be interviewing undergraduates and graduate students at the University of Tennessee at Knoxville on October 27, 2006 October 20, 2006 for positions in IBM Global Business Services-Application Services. We’ve been hiring experienced professionals all along for several years but this is my first personal experience interviewing college students for entry level positions. I like to look at it as hiring the next generation of I/T Architects and others who will become the technical leaders of tomorrow. Think about it. This is a clear indication of confidence in our future prospects for new business and demonstrates a willingness to invest in the training and mentoring of new employees who don't have lots of real-world experience.

I was actually on campus a couple of weeks ago to speak at an "info night" to talk about Application services and what career in consulting is like. Here's a picture of the UT University Center.

Monday, September 18, 2006

De-Nerding Your Geeks

It seems that everywhere I am reading another article in some trade rag about the need for technology people to have "soft skills" and be able to communicate with non-techies. Here's a quote from a particularly good example that I stumbled across from the Australian version of www.cio.com. It goes so far as to quote one frustrated CIO who said 'Forget the technology skills, give me business skills and I'll teach them the technology'.
"I don't know what exactly happened, but when the program director came back he was very concerned about the project. I had expected him to be pleased," Setty, now chairman and chief evangelist for US-based Cignex Technologies, says. "I asked him what he was concerned about."

It turned out that program director had asked programmer whether he could make some changes to the program, and if so, how long they would take. Programmer, thrilled at this unexpected chance to flaunt his ability, had launched into an elaborate rundown of the work involved. As a result, program director got intricate details of child and parent windows and other jargon the intensely non-technical director could only translate as gobbledygook. That led program director to two misguided but deeply disturbing conclusions: the team was doing something like rocket science, and there was great strife ahead. "I asked him for a simple change. Now it looks like it will take three days and there is a risk to the project," the program director complained to Setty.

Setty soothed program director's ruffled feathers and assured him his team could indeed make the changes with little risk. That left program director with just one question: "Are you sure you've got the right team for the job?"

Of course, hardly anyone sees today's CIOs as geeks: most CIOs long ago discarded their white socks and sandals for the business suits that gave them passage to the executive suite. But the best laid plans of CIOs can and do often "gang" astray when the geeks who work for them slip their restraints and rub shoulders with - and the sensitivities of - non-geeks of influence within the organization.

Too Many Egos, Too Little Time

"My organization has plenty of people with massive egos that need to be soothed," says one CIO. "If they're having trouble with the computer I can't send some punk into the office who mumbles, won't look them in the eye and grunts, or next thing I know they're on the phone saying: 'I'd like to be treated with respect. I tried talking to him but he couldn't even be bothered answering me'."

So having expelled every last shred of geek-hood from their own bearing, CIOs must now find ways to start purging any symptoms of same from their staff.

"One of the biggest things that geeks have to learn is how to communicate with a non-geek," Setty says. "It's so important. The reason is, the budget most of the time lies with the person who is not a geek: it's with the CFO or a line of business manager. Typically at that level IT staff can't go down to the details of how exactly the software works. These managers just switch off if the geek starts explaining why this 'thing' happens," he says.

Many CIOs have become so sensitive to these difficulties that finding IT staff with business skills is becoming a major preoccupation, says Gartner Executive Programs managing vice president Mary-Anne Maxwell. "CIOs know IT staff need those business skills, and it's getting to the point that a lot of them are now saying to me: 'Forget the technology skills, give me business skills and I'll teach them the technology'. Over the long run that is more important than hiring a person who has a particular outlook on a technology that day."

For more fun reading, check out: CIO | De-nerding Your Geeks

Wednesday, September 06, 2006

Cultural Diversity for I/T Architects

I found myself appreciating Scott Mark's reaction to his first visit to China. I had a similar reaction to India two years ago. Take a look at Application Architecture for the Enterprise: China and the Swarm


"China is amazing in many ways to me. For one thing, it's an incredibly pedestrian society. It's lightweight and limber at the lowest levels. Buildings are literally flying up all around Shanghai, and yet you see the bricks arrive on site via handcart and bicycle basket. I can't imagine the amount of goods in China that are hauled around by individuals rather than machines. Is that inefficient, or the product of a behind society? I don't think so. I think it's amazingly limber and responsive. The West is in the process of trying to discover or re-discover the swarm. China is the swarm."

Wednesday, July 26, 2006

Hot Skills / Cold Skills - What's the Near-Term I/T Future?

I’m sure I am not the only technical professional who has pondered questions like:

  • Are my skills becoming obsolete?
  • Am I becoming too expensive to do the things I’m good at or like to do?
  • What kind of skills do I need to develop to stay gainfully employed? (keep from getting fired - play defense)
  • What kind of skills do I need to thrive in the future? (get promoted - play offense)
I stumbled across a ComputerWorld article by Stacy Collett entitled “Hot Skills, Cold Skills: The IT worker of 2010 won't be a technology guru but rather a 'versatilist.'

In the article she has some interesting quotes such as:
  • “The most sought-after corporate IT workers in 2010 may be those with no deep-seated technical skills at all.”
  • “IT departments will be populated with "versatilists" -- those with a technology background who also know the business sector inside and out, can architect and carry out IT plans that will add business value, and can cultivate relationships both inside and outside the company.”
  • “the skills required to land these future technical roles will be honed outside of IT. Some of these skills will come from artistic talents, math excellence or even a knack for public speaking -- producing a combination of skills not commonly seen in the IT realm.”
Check out the article. I’d love to hear from others about what skills they think it will take to “play offense” and thrive as an I/T Architect in the near future.

Also, for anyone who has had their head in the sand, you may want to see these for a little motivation to consider the future. (hint) Both of these are focused on the latest and greatest SOA technology, not legacy code.

You may also want to check out some of my previous posts which address similar issues related to our changing and evolving careers:

The Globalized I/T Architect

I Really Am a Master Certified I/T Architect

Are All the Good I/T, Science, and Engineering Jobs Going Overseas?

The Role of the Business Transformation Architect

A Culture of Innovation? Or NOT?

How to Become More Creative in Solving Problems

$1 Billion Investment in "Info on Demand"

Are you Pi-shaped?

Epidemic Career Advice

SAP Disrupts Everything

Naming Well, an Essential Skill of an I/T Architect

Vendor-Neutral I/T Architect Certification Program

I/T Architect Certification Revisited

Copyright © 2006 by Philip Hartman - All Rights Reserved

The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.



Thursday, June 15, 2006

The Globalized I/T Architect

There was a lot of fanfare about the IBM "town hall" in Bangalore, India recently. My teammates in Bangalore all got to attend. Based on the Tuesday morning conference call comments, it was a big hit over there

Sam Palmisano, also had some interesting words in the Financial Times the other day. Basically he said the multi-national corporation is dead ... to be superceded by "the globally integrated enterprise." I have no way of knowing how much of this is truly original thought but I would point his comments out to readers.

All of this globalization has a huge impact on those of us who have to shepherd complex software projects along. The globally dispersed development model is alive and well. I suppose, however, that almost any big company that might move a lot of software work offshore has already done it. So now what happens? What does this mean for us as "high wage country" I/T architects? Here are a few thoughts:

  1. Whether we like it or not our job often become to ensure that the global model chosen by the bosses way above us is succesful. Project sabatoge to get them to change their mind is career suicide.
  2. Our job will be getting even more consultative. We will likely spend even a greater percentage of our time worrying about business requirements.
  3. Our "Soft Skills" become even more important as we spend more time writing, presenting, facilitating, persuading, planning, coordinating, selling our ideas, etc.
  4. We'll focus more and more on the things which must be done face-to-face with the business users, excutives, clients, etc. If you can do your job over a VPN from your home office, beware because the job could probably be done from the other side of the world.
  5. We'll write more documentation than ever before so as to enable the armies of offshore developers to be successful (see #1). More and more we will be successful when we achieve results thru others. (Almost sounds like management doesn't it?)
  6. The offshore teams' work will move "up the food chain" to become more and more strategic. See a URL I've pointed to before, IBM to invest $200 million in Global Business Solution Center. The technical lead for this effort, Ray Harishankar, was recently appointed an IBM Fellow, the highest level a technical person can achieve in IBM. There are only 62 of them today out of over 300,000 IBM employees.

Copyright © 2006 by Philip Hartman - All Rights Reserved


The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Monday, June 05, 2006

I Really Am a Master Certified I/T Architect

I have previously blogged about the on-going efforts for vendor-neutral certification of I/T Architects, The Open Group which is running the program, how the goal is to get this certification as widely recognized as the PMP certification for project managers, and how IBM was the first employer to have its internal I/T Architect certification program "accredited" by the Open Group. (Drum roll please...) I would like to officially announce that according to the Open Group I am now a "Master Certified I/T Architect".


Anyone who would like make sure I didn't make this up may do so by going to the directory search and using "IBM Corporation", "Hartman", and my personal confirmation code of "ART_SCI_ITA" as the search criteria.


Copyright © 2006 by Philip Hartman - All Rights Reserved /p>

The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Friday, May 26, 2006

Are All the Good I/T, Science, and Engineering Jobs Going Overseas?

Over the last several years, I have endured much gloom and doom talk among I/T professionals about the evil influence of offshoring of I/T jobs to India, China, and other lower-cost countries with large numbers of highly educated workers. The mood around me seems to have improved over about three years ago from one of panic to one of acceptance (or is that resignation that offshoring isn't going away?).

I recognized early that one important enabler of this business model was the wide availability of inexpensive and reliable telecommunications. This allows, for example, me to have my regular Tuesday and Thursday morning conference calls with my co-workers Bangalore without anybody really worrying about the cost of the phone call. I do, however, remember making my own jokes about how the US needed the CIA to put some Navy SEALs in mini-submarines on the floor of the India Ocean to cut the fiber optic cables heading to India.

As a sign of the improved relationship with my Indian friends, I got brave enough to share my joke with one of our programmers from Bangalore. I was pleased to find he took my joke in a good natured way and countered my joke with a laugh and something along the lines of "Oh... we have so many redundant lines we'd be ok in Bangalore. But Pakistan... if you cut one fiber optic cable the whole country would be out of business!"

I've been a little behind in my blog reading and I stumbled across a gem on Irving Wladawsky-Berger's blog. He's the IBM Vice President, Technical Strategy and Innovation. He has a posting entitled Skills, Jobs, Competitiveness, and Innovation which address the comment I've heard many times from I/T professionals "I wouldn't let my child go to college to major in computer science." He makes several good points:
  • According to the Association of Computing Machinery (ACM) the size of the IT employment market in the United States today is higher than it was at the height of the dot-com boom.
  • Information technology appears as though it will be a growth area at least for the coming decade, and the US government projects that several IT occupations will be among the fastest growing occupations during this time.
  • And... like we in leadership positions in custom application development business at IBM Global Services have been preaching to our practitioners... the role of the I/T professional in the US and developed countries is changing to one which is more consultative vs. heads down pounding code into the keyboard. Soft skills and business knowledge are becoming more important. "These new jobs are much more collaborative, interdisciplinary and broad than in the past. They require solid technical competence, combined with industry, business and management knowledge as well as good communication and interpersonal skills."

I will add this one cautionary note. The attitude now is both that offshoring is not going away and that decision makers will lead with offshoring. By "lead with offshoring" I mean that almost any big project will be assumed from the beginning to be delivered by a globally dispersed team. For consulting organizations, that means the first proposal will already have global resources baked into the projected costs. (If for no other reason than the assumption that the competition will.) For more evidence see IBM announced a $200 million investment.

Copyright © 2006 by Philip Hartman - All Rights Reserved


The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Wednesday, April 19, 2006

Epidemic Career Advice

A friend recently loaned me a thought-provoking book called The Tipping Point: How Little Things Can Make Big Difference by Malcolm Gladwell. The general subject is how epidemics spread. Not just diseases but more importantly - epidemics of information. What starts fashion trends? How does word-of-mouth lead to a restaurant becoming wildly popular? Why are some advertising messages memorable and why do others flop? Click here for a summary of the book’s primary points and definitions.

When I was about half way through the book I commented to the friend who loaned it to me how much I was enjoying it. He runs his own Real Estate Title business and he commented that the book changed the way he looked at his career and the way he runs his business. He explained that a lot of his business comes thru referrals from real estate agents. Around Christmas time and New Years, many businesses like his invite customers, prospects, and business partners to parties. He said he had done that before but after reading this book, he decided to wait until after the usual party rush. He threw an “Equinox” party in March and invited all the real estate agents around him. He was amazed at how many people called to ask “What’s an equinox party?” and how many more people showed up for this unusually named event than had showed up at Christmas parties in previous years. The equinox message was “sticky”

His comment got me thinking, “Is there an application of The Tipping Point in the field of Enterprise Architecture or in a successful I/T Architect career?”

In the book, the author identifies a “Law of the Few” which describes how an epidemic can start with only a few people... if they’re the right kinds of people:

  • “Connectors” – People who know lots of people. People other people want to know. They are “social glue”.

  • “Mavens” – People who provide us with new information. People who accumulate knowledge but are not passive collectors. They want to share what they know. They educate and help without persuading.

  • “Salesmen” – They persuade us when we are unconvinced. They get us to make decisions or change our minds. They build trust and rapport quickly. They infect others with their emotions.

The author also says that in order for a message to spread rapidly, the message has to be “sticky”... an attribute called the “stickiness factor”.

Another important consideration is what Malcolm Gladwell calls “The Law of Context.” Rapid spread of information, rumors, opinion, disease, etc. is heavily dependent on the conditions and circumstances of the time and place.

Back to the question, “Is there an application of The Tipping Point in the field of Enterprise Architecture or in a successful I/T Architect career?”

Is, for example, all the current focus on Service Oriented Architecture (SOA) an example of an information epidemic? It seems that not too long ago, only the true “early adopters” of technology were taking it seriously. Now, even some of the more technology risk adverse companies are taking notice. Is the SOA message “sticky”? There are certainly a lot of “salesman” out there extolling the virtues of SOA. There are certainly a lot of I/T Architects who want to be "thought leaders" in this area. The concept of being a thought leader certainly seems like being a “Maven” to me. Am I an SOA “connector” by virtue of the number of people in my email address book, the number of visitors to this blog, the number of people I’ve talked to on IBM conference calls over the last 13 years, and the number of clients I’ve shared a whiteboard with? All this talk about SOA also comes in the context of many companies moving from mere cost cutting to seeking business flexibility to chase “top line growth”. And what about the “resume” factor as epidemic context? I am sure there are thousands of technologists who all want to make sure their resume contains real-world experience with the latest buzzwords and alphabet soup just in case the next round of “business transformation” has them looking for a job soon. That context certainly makes one segment of our industry very receptive. (It may be a little off topic but check out Scott Mark’s “Resume Points to Consider if You Want a Job at a Large Enterprise” and James McGovern’s “Enterprise Architecture and Resume-Driven Design” for some good discussion on this.)

Returning to my friend with the Real Estate Title business, what should I do to take advantage of these concepts to enhance my I/T Architect career? What follows is my attempt to cast the characteristics of an information epidemic into career advice.
  • Be a connector. Spread the word of another’s success. Know who to talk to that knows people. Be a friend just because you can. Don’t worry about whether there is something in it for you. If all your friends are in I/T, make a conscious effort to cultivate personal relationships in other areas.
  • Be a maven about something someone cares about. We all need to have some expertise that others value. More importantly, don’t hoard your knowledge. Help others be successful. (The Golden Rule comes to mind.) Pass lessons learned (good and bad) on to others so they can benefit. Educate others respectfully for their benefit. Expect to learn something valuable in the process but something probably unanticipated.
  • Though some I/T Architects may consider it “going over to the dark side”, be a salesman. Maybe you don’t sign up for a real sales quota ($$), but be able to persuade others and sell your ideas. It is also important also to be able to translate back and forth between business and technology domains and be able to communicate costs and benefits to both sides in their language. Be enthusiastic about what you’re doing let it infect others. Be trustworthy.
  • Make your architectural messages “sticky”. State your message in a way it will make sense to the hearer and in a way it will be memorable. See also my previous post “Naming Well, an Essential Skill of an I/T Architect”. Looking back on it, I think that good class names, method names, variable names, pattern names, etc. are “sticky”. Learn to judge how much detail is just enough for the listener and how much detail is too much for them.
  • Be aware of the political context. I used to call this “political awareness”. Be aware of what is keeping your client up at night. Be aware of which “boat anchors” (an architectural anti-pattern) are out there that nobody will criticize because the guy who bought it is too powerful and won’t admit to making a mistake. Know how to work your organization’s budget cycle (or your clients). Also it is good to know what is keeping your customer’s customers awake at night, too. Be aware of which decision makers are “movers and shakers” and which ones are coasting to retirement. Know who has influence even if they don’t make the decision.
  • And here's the hard one. Don’t be afraid to be part of an epidemic. Ride the wave fearlessly. Enjoy the process. Stretch the envelope. Get out of your comfort zone. See also "The Value of Rough Seas." Now if only I can practice what I preach.
"A smooth sea never made a skilled mariner." -- English Proverb



The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.

Tuesday, February 21, 2006

I/T Architect Certification Revisited

I previously blogged about a Vendor-Neutral I/T Architect Certification Program sponsored by The Open Group. I noticed recently that IBM became the first employer to have its internal I/T Architect Certification Program “accredited” by The Open Group. This was effective January 26, 2006. I believe what this means is that I/T architects who work for IBM and are certified by internally by the IBM I/T Architect Program will also qualify for The Open Group I/T Architect Certification. (For anybody who cares, I've been an IBM-Certified I/T Architect since July 1996.) The Open Group calls this “indirect” certification. I expect HP will also get their I/T Architect certification program accredited as well as HP is also a “Platinum Member” of The Open Group. If your employer does not have an accredited certification program or you are an independent, you have the option to get a “direct” certification. See I/T Architect Certification for more details.

The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.