“The executive’s job is to take risks, not to…”

“The executive’s job is to take risks, not to avoid them.

A senior executive’s job is to manage risk. We often interpret this as reducing or mitigating risk. But really the executive’s job is to take risks, not to avoid them. Since all action directed toward the future is risky, the executive must decide which risky actions to take and how best to take them. Investing in the stock market is risky, but if you want to earn a return, you have to do it. You balance risks and returns, and choose investments.

The simple reason that the contractor-control model of IT breaks down is the presence of uncertainty. Plans are made with an eye toward the future, but the future is largely unknown. Thus, rigid adherence to a plan cannot be effective—at best, the plan is valid only as long as the assumptions it makes are valid. The seated CIO is the one who tries new foods—well, if they look edible.

The presence of uncertainty is the simple reason why Agile approaches work better than plan-driven approaches—it is also the reason why a good IT leader will often have to make “wrong” decisions. An IT leader adds business value by adopting an intelligent attitude toward risk.”

Mark Schwartz – A Seat at the Table: IT Leadership in the Age of Agility

“Requirements simply don’t exist…

“Requirements simply don’t exist. A requirement, by definition, is something required: the basis for a contract, a way of managing an external service provider, part of a deal where a buyer promises money and a contractor promises to deliver something well-defined. But within an enterprise, what does it mean for something to be “required”? A requirement purports to express a necessity, but where could this necessity come from? In a publicly held company, maximizing shareholder value might be a necessity, but how could a particular feature of an application be necessary when there might be many other ways of maximizing shareholder value?”

Mark Schwartz – A Seat at the Table: IT Leadership in the Age of Agility

Header Image: A spring sunrise taken on one of my pre-work walks. This was one of those cold and crisp days when sunrise often seems so vibrant.

“it’s not enough to get the design right, you’ve got to…

“it’s not enough to get the design right, you’ve got to design the right thing”

Bill Buxton – Designing the future with the help of the past with Bill Buxton

More complete quote:

Problem-setting is basically, it’s not enough to get the design right, you’ve got to design the right thing. And so, if you just leap in and start building something where you’ve got a solution, you have no idea if that’s the best option. There might have been a better way and you didn’t take time because you are already behind schedule. But here’s the crazy thing. At the beginning of the product cycle, you have a small team just getting going. Your burn rate, in terms of what it’s costing you per week in terms of the project and that, is very, very low. So, what you then should be doing is thoroughly exploring a range of different alternatives. Problem-setting, part of that process is this notion of, you cannot give me one idea. You have to learn how to work quickly and give me multiples. That’s a technique for this whole issue of, how do you deal with the problem-setting? And by exploring the space first… oh, that’s the real problem… Put it this way. You have a bunch of people that talk about user-centered design. And they’ll say, you know, go talk to your users and they will tell you what to do. Okay. Would you go to a doctor where you walked in, and the doctor said, okay what’s wrong with you, what operation do you need and what drugs should I give you under what dose, right? And that’s how some people naively interpret user-centered design, is “listen to users.” And, no. I’m going to ask you all kinds of questions. But I’m going to take all of those as part of the information that helps me make a diagnosis. And so, where do we collect the symptoms to find out where the real problems are? You’re telling me this. I understand the situation. Now, I have to know enough about your industry to ask pertinent questions. And for me, that’s what the problem-setting is. The designer, the main equipment is to have that meta-knowledge. And that’s where the diverse interests come in, so how do you get that knowledge? But if you don’t even know that’s the kind of knowledge you need to get, you’re not even going to go looking for it.

“Technology is neither good nor bad; nor is it…

Six Laws of Technology

  1. Technology is neither good nor bad; nor is it neutral.
  2. Invention is the mother of necessity.
  3. Technology comes in packages, big and small.
  4. Although technology might be a prime element in many public issues, nontechnical factors take precedence in technology-policy decisions.
  5. All history is relevant, but the history of technology is the most relevant.
  6. Technology is a very human activity – and so is the history of technology.

Melvin Kranzberg

“Two percent of the people think; three percent of the people…

“Two percent of the people think; three percent of the people think they think; and ninety-five percent of the people would rather die than think.”

George Bernard Shaw

(I don’t think that there is any scientific basis for this quote 🙂 )

“In order that people may be happy in their work… John Ruskin

In order that people may be happy in their work,
these three things are needed:
they must be fit for it;
they must not do too much of it;
and they must have a sense of success in it.

John Ruskin, 1851