Technology knowledge vs Business domain

Francis posted an interesting tidbit about the technology totem pole. It got me thinking about it. Francis took the technology angle an dived. The perspective I would like to take is one of a balance to explain the sometimes condescending behaviours of programmers. If we think of a spectrum in software you have one end which is pure technology, and the other which is pure business.

In mind mind the technology end is where one will find Linux Kernel Hacking, C++, etc... While at the business end one can find more the VB like skills. At the technological end we have functionality based engineering, while at the business end we have task based development, business needs. The business end of the spectrum is you've guessed it by now much more rooted in solving a problem for a business to go better, faster, bigger with much more efficiencies with no degree of separation or very little between the end result(the need) and the software person/team.

At the technology spectrum end most of the time for the kernel hacker the link to a very specific business improvement in a given project is not there. How many times have you been in a discussion where - if only the kernel could do this, then I would rack in that much more money. The point is many more avenues will be explored before one even think about the kernel, so the connection to the business is not nearly as strong.

The reality, and this is where I high five Francis', in my my mind if I'm from one end of the spectrum and I want to go work at the other end I will have a steep learning curve. In one case it maybe technological, and in the other it will be in business "saviness". Neither one can't be taken lightly they are both crucial to the success of any given project.

Microsoft SharePoint is a rocket ship

From Networkworld this platform is becoming a juggernaut, 1B already. My perspective, we've done projects on SharePoint, and we've always ran into some API immaturity. Nevertheless I believe it's a strong platform and a powerful one, MS is making it better with each release. The market can't seem to have enough of it. The projects we have done and are doing are pushing the limit of sharepoint, because we're developing add-ons to facilitate the co-existence of our clients product with Sharepoint. This intersection of two product lines to create something that will leverage each products strength is never a walk in the park. What is required from the two products is not all there, and some serious architecture work must be done to implement the missing functionality on top of the existing API. SharePoint is in the fast lane, and we're right there, and more than ever this is really a fluid environment, one where our creativity is put to test daily.

Macadamian in the Global Services 100 Companies!

From the congratulations-to-the-whole-team-dep - Macadamian made it on the Global Services - The 2008 Global Services 100 Companies this year. As Matt mentioned - A few years back we set ourselves the objectives to be among the top firms in the world, this year's selection shows we're making our way there, and this is a good thing(tm) as Martha would say(Martha Stewart, and don't ask why I know).

Outsourcing Humour Part III

Here is another take at a common misunderstanding in outsourcing!

Outsourcing Humour part II!

As a follow on to my first post on outsourcing humour. You need people that are versed in more than just code, or pop corn!

Outsourcing Humour

Here is a tongue in cheek cartoon as to what we have heard on what is going on some projects in Product Development Outsourcing.  Sometimes you need exactly what you ask for ... but not at all what you need! The moral of the story : A partner who can can finish your sentences and read between the lines doing more than just code is what one needs!

The batting average!

I remember Mike Cowpland saying once "no one has a 1000 batting average in R&D", and it's true. So because of that fact what has happened - companies developing products have cut cost in Manufacturing, ship the manufacturing to China, and then start breathing again. That has worked for a few years, but then more pressure comes along, so they start shipping the product software development Globally, start breathing again, and that has also worked for a few years as well. So the reality has been for product companies:

1. Reduce Manufacturing Costs
2. Reduce Software Development Costs

What's next - we know prices aren't going to go up, they are bound to the law of gravity. The next thing is going to be for the years to come:

• Reduce the failure rate

The third installment of the evolution of product creation, making sure you get the RIGHT product out of the gate! Shareholders are getting tired of paying for R&D efforts falling flat in the market place. They want Companies to bet on the RIGHT product. For 10 product initiatives in most organizations, the vast majority is not going to go anywhere - and 1 is going to be a winner. In consumer speak, the product I buy has roughly the cost of 9 not so great products embedded in it. A big part of the answer is in Design - it will greatly improve the odds for a successful product. Design helps create product that will be quickly adopted with users getting passionate about them. Design executes both with the user context and the Corporation objectives in mind. , Design speaks to the objectives of the corporation, the functionality that can be put forward, and last but not least the task users would be performing with such products. Creating a successful product is cost, time to market, quality, but it also creating the RIGHT product. Creation/Ideation is not done in a vacuum, speculating what the user needs, we need to involve the users. This is our motto at Macadamian. Apple certainly got that, Microsoft also, they have one of the biggest UX lab in number of experts under one roof.