IT Strategies from Window NT 3.51 to the Cloud Era – Part 1

Because hope don’t float!
This is part 1 of a series on IT Strategies. Just some musings. You can find Part 2 here: https://blog.workinghardinit.work/2010/08/14/it-strategies-from-window-nt-3-51-to-the-cloud-era-part-2/
Not many people I meet in businesses seem to be able to define “ICT strategy” without playing some sort “Bullshit Bingo” I’ll give you my opinion. During my years in IT I’ve read and thought a lot about the value of what we design and build. What you’ll find here stems from well over a decade of reading, thinking, working, discussing and helping to develop IT Strategies with colleagues, businesses and consultants whilst exploring ways to deliver value through ICT. One thing I should perhaps add that I have never been in a sales role, so this is not from an account manager’s perspective. But I do recognize and accept that everyone whatever his or her function has a “sales” role in order to be allowed to execute ones proposals. I owe a debt of gratitude to so many people over the years who have helped shape my vision on IT. There are so many voices and opinions, some I agree and some I disagree with, that have influenced my ideas, that in the end all of what you read here is a collection of all those opinions combined with my interpretation of them. Part 1 is about where IT strategies fit in and why they are. Part 2 will address my opinion on how to achieve them.

Introduction

The reason you hear more and more about strategic IT and commodity IT in recent years is due to the attention cloud computing is getting in the media. One of the main forces driving the cloud computing business is economic pressure and the need to provide affordable, scalable IT in a commodity market. Combine this with the “discovery” of business and IT alignment by main stream management and the “strategic” plans will flow abundantly. They’ll almost certainly throw in an “IT needs to learn it’s here for the business needs”. What does that really mean? That management is not capable of using IT for its business needs and allows money to be wasted. Whose responsibility is that? What if they let the same happen between financials and sales? In my humble opinion main stream business managers urgently need to make the effort to learn about the realistic use and benefits of IT. A divide between business and IT is a manmade artifact and not something natural, it is a result of management failure. Bar the stereo type nerds, I see more efforts of IT managers & architects to think business minded than by main stream management in thinking about using IT as a true competitive differentiator. Once the words economy and competition are in play you start talking strategies, just like the military. That’s not a coincidence. Take away the niceties and business is a non-lethal form of warfare. I guess that’s why “The Art of war” was or is such a popular book in top business circles. Just do an internet search for “The art of war business strategy”. The correct definition of what strategy means is out there in plain sight for all of to read and learn.

So why is it that when talking about strategies, ICT related or otherwise, you rarely get a solid response that truly addresses the subject? People seem to mistake simple long term planning and goals for strategies. Plans are used to realize strategic goals; they do not define a strategy. A strategy is what you will do to out flank your competitors to gain an advantage. That advantage, in today’s world, means being different and good. It is almost certainly not about being the best. What is best depends too much on the unique situation of every organization, its specific needs and circumstances at that moment in time. It’s indeed all rather fluid and dynamic, so “best” is very time limited. Anyway you’d better have something that differentiates you from the competition in a positive way. Otherwise there is no compelling reason to become your customer.

Why is having a unique approach and being good at it so important? Being the same as anyone else makes you plain, a commodity that’s readily available. If on top of that your customer’s service sucks, you’ll start losing customers as no one is willing to pay for that. This drives down prices even more and robs you of all potential benefits of any unique selling points you might have. That is far from competitive. Unless your aim is to become king of low priced, bulk delivery for a product that doesn’t require services whatsoever that’s a bad strategy and even then you will have to be better than your competitors in that particular playing field. You have to stand out somehow.

Also, a strategy has to be correct and honest. False assumptions, self-deception, faking and lying as in “methodology religion” will make you lose all professional credibility with your personnel and investors. Once you’ve sunk to that level there is little or no hope of ever recovering from that position. You really cannot get away with faking a strategy.

So what is “my” strategy as an infrastructure guy in a business world to make sure that we are different and good? Well, you already read the appetizer, now read on to find out. And believe me, you need to find out! Way too many business & IT strategies are esoteric boardroom level documents that have little or no correlation with the reality in the trenches. They are made to have some checkboxes ticked on an audit report or are actually just plans with not strategic content what so ever. Sometimes you really wonder why they even bother making them. At least they could have avoided wasting the time and effort.

Defining how the ICT strategy relates to the business strategy

Before we can define what makes a good ICT strategy we need to talk business. It needs to be a part of the strategic business plan or you shouldn’t even bother having one. Oh, and by the way, if you don’t have a high quality business plan made by and supported in actions by knowledgeable, passionate, driven, motivated and hardworking management, walk away. No good ICT strategy will ever come from such a situation. Buying technology cannot fix organizational problems. Please repeat this last sentence at least three times out loud. You need to hear it and let the message sink in! In such a situation having an IT strategy is the least of your problems.

We already stated that a strategy is about distinguishing you from your competitors. This can mean many different things depending on the circumstances. Better products, the same product but with better services, cheaper but good enough for its purpose, etc. Be brutally realistic. If what you do does not set you apart from your competition in a positive way, you have no strategy or have been ill advised on what constitutes a strategy. The fact that “no one else does what we do” is not a strategy, it will not last! The fact that people are obligated to use your services by law is not a strategy. It might be a short term advantage, but it creates no good will with your customers, especially not if your services or products are mediocre or bad. And please be more than just be the odd one out, sure you’re different but that’s not the different you’re looking for.

You must also realize that strategies have a limited shelf life. Sooner or later your competitors will realize what your strategy is and if it works they will start copying it. More often than not they will add some improvements having the benefit of 20/20 vision through hind sight. This means that, over time, what was once a distinguishing solution that gave you a competitive advantage becomes a mere main stream commodity. Now please realize that being a commodity does not mean irrelevant or useless. Power, heating, fuel, telephones, e-mail, storage, file servers… are all commodities we cannot do without! But in the commodity sector you will compete by being different in pricing, quality of services and added value. Only when technology becomes a blast from the past by significant advances or changes in science it becomes economically useless. Think steam engines … but … retro does exist and come backs do occur. Windmills any one?

I know the cloud hype recuperates just about everything that is delivered can be over the internet and is service oriented but please realize that not all commodities are or will be services.

clip_image002[5]

Given the fact that strategies are far from long lasting entities, what does this mean for an IT strategy? Simply put: speed and agility are of the essence. We must be capable of moving fast and decisive. There is no time anymore for years of thinking, contemplating and testing. The long term vision must still exist and it is extremely important, but it is not the same as a strategy. To reap the benefits of long term thinking one needs to survive long enough to be around! 15 year long term strategies are doomed. These are day dreams. A bit like the Maginot Line the French build for over a decade but was utterly useless as its concept was out of date by the time World War II broke out. Long terms visions are realized through several sequential and adaptive strategies. As you can see in the figure with time strategic solution becomes a commodity and a part of the IT infrastructure that needs to be maintained. A good strategy takes this into account so that the strategic solution can evolve into an operational and tactical commodity instead of a very expensive drain of resources.

One could say that all IT can be found somewhere between following states:

· Strategic: Technology that differentiates us in support of (new) business strategies. This is what makes us more competitive, that adds value, because it’s unique and innovative.

· Commodity: Stuff we need but no longer adds competitive advantage. It does provide tactical or operational benefits and you can’t do without them. Make note, strategic commodities exist, oil is a prime example, water another one. So commodity is not a synonym for low value, it just doesn’t add value in itself or no longer serves as a differentiator.

Everything else, whether it is cheap or expensive, subsidized or self-sustaining are frankly technology hobbies (not in the picture). Where are the value and the profit? Management should avoid this. The best thing that can happen here is that you actually learn something building & maintaining it or use it as a lab for creative innovation. But that’s not a hobby anymore … that’s a dream job for engineers.

Tell me what an ICT strategy is already!

An ICT strategy supports the business initiatives that provide a competitive advantage to an organization in such a way that it does not become a pain in the ass over time. Only incur technology debt where and when needed and manage it carefully. But how the hell does that materialize in reality you must be wondering by now? Well it is the combination of creatively building, deploying, operating and using solutions that deliver value by making you more competitive. Solutions scan be realized using standard software and hardware, with custom build applications or a combination of both. Whatever the case … the solution requires very knowledgeable people, serious skill sets, a mind driven by curiosity and the need for results.

People buy results, not services or efforts. This is one of the big mistakes in the thinking of many modern so called service driven companies. They fail to provide good services, let alone results. They are in effect just low cost / low value operators. If you provide services they need to be there to produce the results. Otherwise you are, for all practical purposes and intent, lying which will come back to bite you. Take note however that too much service is financial suicide. Don’t cater to individual and unique needs unless that is your core business.

Since solutions are custom build on development platforms and infrastructure it is critical to realize that the choice of platforms and infrastructures can mean the success or failure for an organization since it directly relates to its ability to compete. Yes, once again, the reason for having a strategy in the first place!

The most common issue we see when dealing with an IT strategy is that many organizations have no clear picture about what they do, how and why. They just seem to do “stuff” and expect of rather hope that hard work and effort will help them realize their goals. But without clear and well defined goals there is no way of achieving them. Efforts and hard work alone will not produce results. Customers do not pay for hard work, they do not reward efforts. That was something that worked in kinder garden but fails in a business environment. Remember, customers pay for results. You cannot buy a product that will deliver these out of the box.

So what must an ICT strategy achieve?

Since we have seen that strategic solutions eventually become commodities, any combination of infrastructure, platforms and solutions must work well during their entire life cycle. Decisions that focus only on strategy might lead to the implementation of the latest and greatest technology. This can lead to very divers, esoteric and heterogeneous environments with very high integration & support costs. It also incurs the cost of finding, retaining and maintaining good developers and engineers with knowledge about such systems.

On the other side of the equation one can not only worry about keeping short- and long-term support costs low. This will lead to missing out on the business benefits that new technologies can bring. In the end finding the right balance between these two is very important and failing to do this will be very costly in financial repercussions, lost opportunities and failed projects. This ends in the downfall of the organization since it becomes irrelevant in the market and has no more means to support itself.

Custom build solutions do not exist in isolation. They need to run on an infrastructure, connect to other systems, be able to be secured etc … This is called integration and if this is overlooked it can become a financial burden that negates the added value of an IT solution and make it a cost instead of an asset. For example “Best of breed” has often failed in the sense that is did not deliver enough value to justify the high cost of acquisition, maintenance and integration. The real killer here is the efforts and thus cost involved in integrating all these. Even if you do get it to work it is often in a way that negates good practices, reduces security and incurs a high, cumbersome administrative overhead which is error prone and expensive. It does make a good revenue stream however for “consultants”.
This is part 1 of a series on IT Strategies. Just some musings. You can find Part 2 here: https://blog.workinghardinit.work/2010/08/14/it-strategies-from-window-nt-3-51-to-the-cloud-era-part-2/

The Architect Virus. Professionalism, Career, Status, Narcissism & Entitlement

What’s with this “Architect” virus going around? Why does everyone want to be one? Is it because of status, narcissism, entitlement, money? No really, why?  I know some architects who work very hard and earn just as much or a little more than most other professionals. Their responsibilities and stress levels are a few notches higher than most however. What about status? That’s just bragging rights. Sure you can inflate you’re résumé or LinkedIn profile a bit with that but that’s about it. You don’t need to be an architect for that. Just call yourself “Senior Master Enterprise Technology Architect”, no need to do anything more than to type it in. Inflation, that’s what it is. Once you needed like 10 to 15 years to become senior at anything. Now 4 years out of school you’re a senior consultant with years of experience. So now we need some more titles to make the distinction I guess. Entitlement? Are you that good? If so how come no one sees it?

OK, so you have big dreams of being an architect. Do you have the skills to go with them? Prove it. Start working as an architect. Act like one, work like one and maybe one day you’ll even become one. Being an architect is not a title, it’s not about how many post grad training you receive or master classes & conferences you attend. It’s not a pay scale; it’s not a promotion or a status. None of these things define an architect, let alone make you one.  It’s all about what you do and achieve. It’s about results and value. Hell, you can have three PhD’s and two Post-doctoral Certified Guru certificates hanging on your wall. Those are all fine, but tell me what your value to the business is? How do you hold up in a passionate discussion with industry experts?

An architect is someone who is capable of designing, building, implementing and supporting medium to large, more of less complex systems in such a way that they function well and that are not or do not become a burden to the organization that uses them. In that respect, my mum used to be a great “domestic architect”. She had a very small budget, big needs for her family and like a true engineer she created very workable and productive solutions with very little money using the resources at her disposal. Al lot of people today couldn’t hack that effort. No way. Did she moan and complain? Occasionally, but most of the time she was working and making sure everyone was taken care of and got all they needed. She never got any status or money for that. No bragging rights, she found satisfaction in doing a great job. She also got some respect.

Why do some people act like spoiled brats? Frequently in direct contradiction with their ambitions. I see this in job applicants, and people on the job at the places I work. There is nothing wrong with ambition, earning your fair share, being rewarded. But all too often people expect this up front. Instead of earning they are into getting mode. That just doesn’t work. You don’t get a job, you don’t get a pay check, you don’t get respect, and you don’t get knowledge. These things are earned, not given. Now there are and will always be bad bosses, exploited employees, dysfunctional organizations and such but please don’t be a narcissistic entitled brat. Don’t complain about problems, help solve them.  Trust me, if you really work in a dysfunctional place beyond repair you need to leave. Run! But if you stay … that’s your decision. Perhaps that pay check and benefits are not that bad after. Or are you, contrary to your ego, not convinced that some other business will pay big bucks for you added value? Whatever the reason is, start doing your job. That is what earns you the paycheck & benefits. Moaning and groaning can be an outlet to vent some steam but it doesn’t solve anything in the end. Don’t give me “It’s not my job”, “That’s not my responsibility”, “My boss should do this and that”, “Someone ought to do that”, “This should be fixed”. Don’t moan when you’re constantly going on about being a great professional, too good to waste your time on the lowly work and are “working on becoming an architect”. It’s bad enough for someone who’s just doing enough to prevent being fired, we can really do without the gripes from someone who claims he’s going to lead. There’s an old army saying: “Shit flows down, gripes flow up”. Your team doesn’t care if you think you ought to be paid more and deserve more gratitude or demand more status.

You’re probably an engineer or a likewise highly educated professional with an above average wage. What do you expect? That they pay you that wage to whine about issues and that “someone” must fix them. Wake up sun shine. That is your job!  Do you really think that the high end wage and great benefits you’re being paid is just to show up and find that the company is running perfectly already? Nope, you’re there to take care of those problems and work towards a better organization. Are you doing that? Are you really sure about that sport? Why on earth do you expect to be patted on the back, made compliments and expect status promotions and raises for sitting around complaining? Take responsibility and build that better organization, that better infrastructure, that better team or that better application. It’s your job, your responsibility. When you’re always in the “what is in it for me” mode, taking care of number one, are you really doing your job?

Leading a team, being a go-to person also means thinking of the team. You need to look at the needs in function of the plans for achieving results, the desired out come and what the team needs to get the job done. If you don’t, you let everyone down. That’s why I am disappointed that the first time people are given the opportunity to put together a conference delegation based on the above mentioned specifications and they do the following: send your themselves. They didn’t make a plan for the team; they didn’t ask around or discuss the needs and plans. They just pocketed a conference or training. “Hey, I’m not being paid to take care of that. My boss should”. Perhaps your boss is drowning in work. Perhaps he could have used some help. Help you could have provided, proving you’re capable of helping the team, supporting your boss and take responsibility”.  If you can’t even get that right, how on earth do you think someone will ever listen to you, follow your lead or give you a promotion? It won’t happen, never, ever. They are just advertising their own short comings for the job they claim they aspire to do.

So do your job well and good. Your job satisfaction will increase, people will notice what you can achieve and will start working with you with greater confidence, enthusiasm & results. Working hard & smart generally leaves you a richer & experienced person. And perhaps, not guaranteed, you might get a raise for that. But even if you don’t your job life will be a much happier one. If that’s not enough for you … well there are plenty of organizations that will hire you and pay you the big bucks if you have such good and in demand skills that deliver outstanding results.

All of this can be summed up in one sentence. Instead of expecting to get things because you think you’re entitled to get them start earning them by working for it. In the long run, what do you think will work out better? Assume the role & responsibilities, do the job before the title and the raise. And no that does not mean you have to work yourself to death. But 9 to 5 coasting never made anyone an expert. Here ends the career lesson.

Direct Access Step By Step Guide Version 1.2 released

I’m about to start work on a Windows 2008 R2 / Windows 7 Direct Access project and while gathering some resources (I played with it in the lab last fall) I noticed the Step by Step guide has been updated to version 1.2 which was published on June 18th 2010. It’s a great kick start for demoing Direct Access in a lab for management. Grab it here. http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=8d47ed5f-d217-4d84-b698-f39360d82fac&displayLang=en. If you’re hooked and need more info, check out the Direct Access pages on TechNet: http://technet.microsoft.com/en-us/network/dd420463.aspx

Some people complain Direct Access is (overly) complicated. Well, it’s not a simple wizard you can run or some SOHO NAT device that you plug in, but come on people. We’re IT Pro’s. We did and do more complicated stuff than that. As a matter of fact I remember some feedback John Craddock got last year at Tech Ed Europe (2009). Some consultancy firm employees told him he should not make it look that easy. Organizations need consultancy to get it right. Really? Some will, some won’t. I have nothing against consulting, when done right and for the right reasons. I even consult myself from time to time with partners who need a helping hand. But take note that the world does run on people, and consultants are people (really!). What they can learn,  you can learn. Just put in the effort. So go have fun setting up Direct Access and giving your road warriors and IT Pro’s some bidirectional and transparent connectivity to company resources. To me Direct Access was one of the big selling points for Windows 7 / Windows 2008 R2. Better together indeed 🙂

Why I Find Value In A Conference

For those of you who are attending a high quality conference I’m going to share some tips. It’s great to be able to attend a conference. Not because it’s in a great city and you’ll get to dine out at night, but because of the opportunities it provides us to learn and grow.

So what is the value of such a conference? Well, it is about the communication with peers and guru’s. The conversations you’ll have and the exchange of taught and ideas. The technical information you’ll gather, the products and techniques you’ll see. All of this will help you to direct and focus the way in which you approach your job, run your projects, plan and realize your visions and ideas. A conference, if done well, is nothing more or less than a technical education in the business of ICT and how to do things and make it work, results versus efforts wise. On top of that you get to interact and share ideas with your peers. You can’t ask for anything more.

Conferences cost a lot of money, time and energy. After all when you’re attending you have no income or the boss pays you while you’re not in the office creating value. On top of that you have to pay for the hotel, flight, daily expenses and the conference fee.  So why would we do this? There’s a global crisis, there’s a European crisis, there’s an XYZ crisis and there is economic doom and gloom all over the place. Not to mention all the results of that downturn … cutbacks, redundancy, foreclosures, failing businesses, unemployment, etc. The conference scene is not immune to a recession. Conferences are canceled, scaled down, attendance drops.  The competition from blogs, on line, free or subscription based content, pre views, beta’s, web casts, computer based training can be felt as well, as has been the case for many years. Conferences need to fight to maintain high standards of technical content for an ever more demanding and skilled public in a very rapidly changing world and IT scene. But still, a conference done right is an investment worth making. It is an investment in knowledge. In return we get all of the above mentioned in the previous paragraph and that is why I attend them. They make me a better “Technical Architect”. That is try I really put in the effort to get the funds, create the opportunity and reserve the time to go. The benefits of a conference, if done right, cannot be denied.

What is the right way?  Well first here’s the wrong way. Don’t go there or learn how to use delegates in .NET or to build a Linq to Wmi query. It’s not just an ordinary classroom. Do not go there to nag about some issues you had or have because you’re too lazy to do research and read help files, readme texts, TechNet or MSDN. Do not go to complain about how hard it is to find information and study.  Do not go because of the great location, you will see nothing of it 🙂 unless you use it as a vacation. Maybe some USA people deserve to do this but heck I’m from Europe and I get my fair share of holidays. Also, take any frustration, denial or ignorance about the lies of instant gratification and careers success you might have had when you bought product X and it didn’t just improve your live after clicking “Next” somewhere else. Results and successes come from an enduring effort, which is a fancy word for hard work. They are not a right, a perk or let alone guaranteed (yeah some vendors and people lied to you, get over it). If you cannot search study and learn on your own get out of ICT now. If you need support for every issue or new item and expect someone to be there to help every step of the way you’re in trouble. It takes time, dedication and a great deal of effort to become and stay proficient in IT. Even then you’ll know about failure, setbacks, troubles and mistakes. Life & work is not a commercial.

Go to a conference for the big picture, the architecture, the networking with peers, the possibilities and the dreams. Expand your knowledge and views on how to make the pieces work and interact. The focus of the conference is on tying it all together, learning new and better ways, discovering possibilities which all equals to yet more stuff to learn and more work to do. At the booths manned by industry experts or representatives do give feedback about the product and offer to send some more details about certain real problems you might have come across. But be nice and polite, don’t be a jerk. Would you feel compelled to help a jerk? Techies are people, really!

Don’t run to sessions like a mad man without a plan.  Know why you are there and how to get what you’re after. If this is your first conference, everything will be new and fabulous (I hope). You can’t attend enough sessions. You are torn between the choice of sessions and tracks. You’re full of new ideas immediately and overwhelmed with even more just after that. So for all you newbie’s, get your act together and prepare a bit or it will turn into chaos. Write down ideas, insights and possibilities to pursue. What about you conference veterans? Have you’ve been there, done that?  Have you have seen it all before? Not really, and we all know it.  It’s all about lifelong learning. Conferences are about being in a stimulating environment where you “marinate” in the professional IT community for a week. Learn from and with the people attending. Not only during sessions. Lunch with them, have a coffee with them. Immerse yourself in this explosion of IT and business. Think about the new stuff, use your imagination, and write down ideas. Cross check your plans. Calibrate you insights.

The role of the conference is get you thinking about stuff and gives you a chance to talk to each other about that stuff. Interact! It is the essence of a conference. Ask questions both in public and in private. Talk to attendees, to experts, to vendors. See what they are in to, need, tried, where they succeeded and failed. Find out what they have to offer. Talk shop, talk IT life, and make that connection with the others attending in whatever role. There is a wide world out there much bigger, larger and perhaps tougher than your own little world that is driven by results and built on efforts. Those folks have professional and business experience in all of the subjects being discussed. Pick their brains! Get some new insights and ideas. Yes I know some vendors act like 2nd hand car dealers and yes I’ve met people who don’t know their own products. But that doesn’t rule out the need for and benefits of communication and interaction, those where just the wrong people, just move along. Oh and don’t forget to get a bunch of extra business cards you got out of the drawer. Also keep in touch with people you meet. Send a follow up mail, a tweet, a blog mention. That’s how you expand your knowledge network. If you get to go to a conference, enjoy it and make sure you arrive early and leave late. There is no value in missing a part of the experience to save some time or some €/$ bills.

I don’t implement all the ideas I return home with from conferences. But I have them written down in mails, scraps of paper, txt files, One Note scribbles etc. I tend to pour them into a word document during and after the conference. Form that I distill my plans, my vision and my roadmap.  I will present those to management, colleagues, partners and customers and offer them solutions based on my perception of what business needs we can satisfy with technology. The stuff I’m working on now was born as ideas 12 to 18 months ago. Those ideas are tested and checked over time, they ripe and then they become plans. I find a conference a great place to do that.