Link Collection — April 28, 2013

  • 49ers Select New Technology For NFL Draft | Only A Game

    podcast / article on SF 49ers use of stats and SAP’s HANA appliance in scouting, drafting. Continues to speak of NBA statistics and further use of HANA in sports business.
     
    “49ers COO Paraag Marathe says piling up information is easy, but the challenge is making it user-friendly for coaches and general managers.

    “And that’s something that’s sort of overlooked. People want to get reams of data and put together like this really robust analysis,” Marathe said. “But you know what? If it’s not communicated [or] it’s not simple and clear, it’s not going to be used.” …

    “Does our simulation make sense  in the context of that team’s roster, that team’s depth charts, in the context of that team’s salary cap? Will they be able  to afford these kind of players, or are they going to make a different trade, are they going to make a different pick? That kind of real-time simulation is the real beauty of this virtual draft board. Otherwise, what you have is those big magnets.””

    tags: nfl sports statistics sap hana

  • Get Innovation Right: Tap Into Women Over Forty | LinkedIn

    “According to New York Times article Innovators Get Better with Age, research indicates that a 55-year-old and even a 65-year-old have more innovation potential than a 25-year-old. He also notes that the directors of the top five grossing films in 2012 were in their 40s and 50s. While Nobel Prize winners may make their break-through discoveries earlier in life – the average age is around 38 – typically it takes twenty years to socialize their ideas, meaning they don’t receive recognition for their achievements until around the age of 60.”

    “Then there’s the research around entrepreneurs. “The average founder of a high-tech startup isn’t a whiz-kid graduate, but a mature 40-year-old engineer or business type with a spouse and kids who simply got tired of working for others,””

    tags: innovation age workforce

  • Does Your Architecture Pass the “So What” Test? | Doug Newdick’s Blog

    Nice reminder and simple check from Doug Newdick. Reminds me of a quote I recently pulled from the New Yorker: “Harm averted is benefit unseen”. Be prepared to show / communicate value, even if it’s for harm averted.

    “Does your architecture pass the “So What” test? Can you demonstrate the specific value that a particular architectural deliverable or activity will add? If not, why are you even bothering? In this case, as with justice, your activity must not just add value, it must be seen to add value.”

    tags: enterprise_architecture systems_architecture

  • 10 Breakthrough Technologies 2013 | MIT Technology Review

    Good list from MIT Tech Review. Several I’ve discussed with a client as they relate to the future of healthcare, and therefore, society. [Deep learning, DNA sequencing, Additive Manufacturing, Robotics]

    tags: technology trends

  • Great Innovators Think Laterally – Ian Gonsher and Deb Mills-Scofield – Harvard Business Review

    “The creative process is just that: a process. Recognizing value that others have missed doesn’t require preternatural clairvoyance. A well-honed creative process enables us to intuitively recognize patterns and use those insights to make inductive predictions about divergent ideas, both vertically within categories, and horizontally across categories. By understanding the genealogy of innovation within a given category, we can imagine what might come next.

    We need to break out of thinking that is solely based on what we know, what we assume, and what we’ve experienced. Many of us are so entrenched in our industries that we don’t know how to think laterally or horizontally. We usually go a mile deep but only an inch wide. We haven’t given our people and ourselves the time and opportunities to explore other industries, cultures designs, ways of being and doing, and other “adjacent possibilities.””

    tags: creativity thinking hbr

  • How Kaggle Is Changing How We Work – Thomas Goetz – The Atlantic

    “Because here’s the thing: the Kaggle ranking has become an essential metric in the world of data science. Employers like American Express and  the New York Times have begun listing a Kaggle rank as an essential qualification in their help wanted ads for data scientists.  It’s not just a merit badge for the coders; it’s a more significant, more valuable, indicator of capability than our traditional benchmarks for proficiency or expertise. In other words, your Ivy League diploma and IBM resume don’t matter so much as my Kaggle score.”

    tags: kaggle datascience workforce

  • Cartoons from the Issue of April 22nd, 2013 : The New Yorker

    Perhaps I’ve spent too much time talking about trend convergences with a client, but this cartoon amused me.

    tags: newyorker cartoons trends

Posted from Diigo. The rest of my favorite links are here.

We’re talking Smart Process Apps — and so is Forrester.

“Smart Process Apps are a reflection of innovations we have been delivering in our business over the past few years — giving our customers more agile work environments, helping them innovate faster, and solving problems that extend beyond the boundaries of BPM for our customers.”

Related posts:

  1. When It Comes to Mobile Apps – Thin is In! One of the big topics of discussion regarding mobile is…
  2. Forrester Ranks Top Business Process Management Suites Yesterday Metastorm announced that it has been recognized as a…
  3. OpenText Smart Process Applications: At the Intersection of Social Street and Core Systems Ave Last week, I helped kick off OpenText’s EIM Days in…

Related posts brought to you by Yet Another Related Posts Plugin.

Accelerating Business Architecture

I have, on occasion, been asked to spend time with an Enterprise Architecture team to help that team improve their maturity.  It’s a great opportunity for me to learn, and share, and work with some of the smartest people on earth: Enterprise Architects.  Coming off of an excellent experience in Europe, I’d like to share some reflections.  I won’t name my client company to save them from any possible embarrassment. 

This was a rather unusual case for me.  Typically, I’d do fairly simple things.  I may review and evaluate some activities, train folks for a day on methods, or perform a maturity analysis and provide a report out.  While each of these require expertise, none are particularly dynamic.  Nothing that would really push me to learn and adapt. Not so this time.

In this case, an EA team, made up of mature, experienced architects, was being challenged by an hard-driving CIO to “climb the ladder” into a strategic role, and do it quickly.  Since the team was distributed around the world, climbing that ladder (which is already difficult to do) was made all the more challenging by the limitations of communication at a distance.  Each of the architects were peers, which meant consensus and a shared vision were critical.  They needed to accelerate their progress. 

First, to be blunt, I’m not new at this.  I’ve conducted trainings and workshops in a wide array of places to a wide array of teams.  I’ve attended dozens of EA trainings and workshops.  I hold two EA certifications (and will soon have a third).    But this particular engagement was challenging.  It was challenging because the objectives were clear, ambitious, and very specific.  Due to the singular vision of one particular architect (who reads this blog… yes, I mean you, PH), I had a very clear set of marching orders: accelerate the team towards impactful and relevant business architecture.

We held a series of exercises over two very full days in a beautiful country inn in Germany.  In each session, I provided some concepts and some practical tips from my own experience, followed by an exercise that got the group out of their chairs and collaborating in teams.  Over the course of those two days, the team decided, for itself,

  • what kind of Enterprise Architecture team they wanted to be,
  • what their vision and goals were,
  • what their specific enablers needed to be,
  • and developed four alternative candidate roadmaps to deliver on their goals.

 

Along the way, we discussed and practiced skills in business architecture, stakeholder relevance, alignment, and roadmap creation.  In the follow-up day, we worked to create visual stories that can be used to “tell the story” of their transformation to their many stakeholders.

Honestly, that’s a hard road.  In a typical EA team, that amount of work takes weeks on a fast track.  I didn’t have weeks.  I had two days.  So I had to dig deep.  Working from every one of the experiences I’ve had in Enterprise Architecture, and thining back on every workshop or seminars I’ve ever conducted or attended, I pulled together an approach that left very little room for deviation from those goals.  We worked HARD, and I can honestly say that I learned as much from this team as they learned from me.  I am so honored to have had the opportunity to work with them, and I honestly hope to have another opportunity someday.

What, you might ask, would the trainer learn from a training session?  Not much, if I were a trainer and if this were a training session.  But I’m not and this wasn’t.  I’m an architect and architecture manager.  I’m an execution and alignment expert.  This was a team of mature, thoughtful, and expert architects, each with over two decades of architecture experience.  No, this was no training.  This was guided empowerment.

When you work with people who are, in all rights, your peers, and you work to create something that you know is magnificently difficult to do, and you succeed, you learn.  I certainly did.  I deepened my respect for the talent and experience of passionate and empowered men and women.   I broadened my skills of consensus and execution under constraint.  I built unique connections upon the ideas and efforts of so many before me who generously gave their time and talent to help me to grow. 

There are ways through the difficult and challenging obstacles that can make life difficult for business and enterprise architects.  There are solutions.  There are options.  There are opportunities.  It takes focus, dedication  and passion to bring them to light.  I was richly fortunate to have a chance to work with such a strong, vocal, and passionate team of people. 

To sum this experience up, I’d like to share my recollection of the words of one of the attendees.  At the closing, we spoke in turn about what we learned during the workshop and what we wanted to say to end it.  One attendee shared this:

When I came to this workshop, to be honest, my expectations were very low.  I had no faith that business architecture could achieve the goals that were being set for it.  I just didn’t see it.  Now, after these two days, I can see it.  I feel like I learned 20 years of experience in two days.  Thank you.

You are welcome.

Categories Uncategorized

Does Your Architecture Pass the “So What” Test?

Does your architecture pass the “So What” test? Can you demonstrate the specific value that a particular architectural deliverable or activity will add? If not, why are you even bothering? In this case, as with justice, your activity must not just add value, it must be seen to add value. A number of recent discussions […]

Systems Flow joins elite group of firms whose IT Architecture methods have been recognized by The Open Group.

Rhinebeck, NY April 23, 2013 – Systems Flow, Inc. announced that the Systems Flow Investigative Architecture™ method has been recognized within The Open Group Certified Architect (Open CA) Program. “A foundational skill for an architect is the rapid ability to assess and document current and proposed solution designs,” said Dan Hughes, Principal with Systems Flow. […]

Categories Uncategorized Tags ,

Scalability and uniqueness

What actually do we mean by ‘scalability’ in enterprise-architecture? What can and can’t we scale within the architecture, or the process of architecture itself? These questions came up for me in thinking about a comment by Dave Duggal to the previous…

How to Become a Hero for Growth

One thing that happens when you work to develop change across an organization: you detect the “cultural” elements of an organization that often go unnoticed by the people involved.  Just as a “Fish discovers water last,” people working in a cultural context can be fairly unaware of the implications of their culturally influenced decisions.  “It’s the way we’ve always done it, here.”

One cultural influence that I’ve seen, quite often, in organizations that are struggling to grow past a particular size, is the “culture of heroes.”  This pattern of behavior has the following smells:

  • Whenever there is a problem with the servers, call Jack.  While it isn’t his current job, he’s the one who installed and designed the server environment, so he’s the logical one to fix it.  (Extend this beyond “the servers.  For every “area” of the system or the business process, there is a “person” who is the “hero” who can solve problems with that area.  There’s often an “uber-hero” above them all, who has to be called in for every emergency no matter what).
     
  • If someone asks me to do my job differently, I refuse until my manager specifically approves the individual change.  After all, my manager has done this job for years and years, and he or she knows best how to do it.
     
  • If I’m a hero or a manager, and I make a casual remark in a meeting that I want to have control over some minor aspect of a process, a subtle but IMMEDIATE shift occurs so that the process now has an extra step: to ask me for my approval of that minor aspect (even if it is something that has little or nothing to do with my actual accountabilities).
     
  • If an important new project is starting, the kickoff meeting cannot proceed unless a couple of heroes are in the room.  Absolutely no way.
     

These are signs of a culture of heroes.

And they are a big problem. 

Let’s first recognize that, for any snapshot of 100 people in the same role, there are two or three that have risen up to become well respected experts.  There are 20 or so that can lead a group, and the rest are following.  One of those “folks in the rest” may mature, of course, and may be ready in the future to lead or become one of those well respected experts.  These are not labels.  But, at any one point in time, the ratios often work out this way.

This is human nature.  Nothing wrong with that.  The problem comes when you feed it.

As a leader, you cannot avoid a variation in skills and experience.  However, the true leader recognizes that there are people who want to grow.  He or she will want to create an intentional culture that not only fosters that growth, but encourages individuals who are the experts to “step aside” a little, and allow the non-experts to have a chance at solving tough problems. 

If your culture keeps coming back to a handful of heroes, no one else in the team can grow.  The people who naturally WANT to grow will leave.  And you are left with an organization of people who don’t want to grow.

If no one in your organization wants to grow, the organization won’t grow.  Plain and simple.

Not only that, your organization won’t evolve.  It won’t improve.  It won’t optimize.  It won’t do ANYTHING interesting or new.  That’s because all the people who could benefit by change, all the people who have fresh ideas and novel approaches and interesting influences, have run away to other organizations where they can try those ideas out. 

And that is what the culture of heroes does… it kills the spark of change in a group of people.

So don’t let the heroes stunt the growth of your organization.  Look around.  If you have heroes who usually get called, ask THEM to be heroes in a different way… heroes for growth.

A hero for growth makes this decision:

  1. I listen when someone brings me a problem.
  2. I consider whether the person who has the problem should be empowered to solve it.
  3. I consider whether the possibility of them “doing it wrong” means that they will cost a great deal of money or some other business loss. 
  4. Then, I take the DEFAULT position of “let the person closest to the decision make it.” 
  5. I only take on a challenge if the people who should be doing it are asking for my help.  (Not their managers, or their peers, or their staff.)  And when I do, I take the attitude that I want to help that person grow… so I challenge them, include them, and inspire them.  When things work, they get credit.  When things fail, I take part of the blame (giving them a safe space to grow).  I don’t override them, belittle them, or ignore them.  I never ever point fingers.

 

If you are a hero in your organization, I challenge you right here to become a hero for growth.  Who knows… you may change your culture just by your leadership, and your example.