In the spirit of accountability, here are my training numbers from January. It was a bit disappointing overall given the strong start I had to the year. The pie chart shows a significant run focus in my workouts this month, with ~ 75% more of my time being spent running than cycling. I did manage to make it to the pool a couple of times, but I kept my sessions short – focusing on the feel of my stroke in the water and trying to not overwork my shoulders.
The performance management chart clearly shows the delineation of school starting back (yes, I’m a 2nd year graduate student at Georgia Tech while still working full time– Insane!!). I had just one good run after that on the 17th, and NADA-ZILCH-NOTHING through 1/31. The weather didn’t help as we had a couple of days with icy roads. Still – that is no excuse to not get on the trainer.
Swim: 1050 yards. 24 minutes
Bike: 70.6 miles. 3 hours, 48 minutes
Run: 37.0 miles. 6 hours, 56 minutes
Other (Tennis / etc.): 0 hours
Total training time: 11 hours, 8 minutes.
Microsoft has released an update for SharePoint Server 2013 that provides a new hybrid crawling feature for search. One of the biggest challenges we face in a move towards the cloud is having a fragmented search experience. Prior to this release, multiple searches had to be conducted across repositories, and there was no way to merge the relevancy rankings. Relevancy scores for on premises results did not merge with the scores from the cloud, so there was no single top-down view of search results. With this release, that is now possible.
My take is that this is not all roses as it may appear. This new feature will “index all your crawled content, including on-premises content, to your search index in Office 365.” This is certainly a step in the right direction from Microsoft, but I’m not sure I where I stand in regards to the approach. The question is in the details of indexing, and how much information gets passed up to Office 365. The potential downside – you may have now created a copy of your on premises content in the cloud, exposing the very legal risks that may have led you to refrain from moving that content to the cloud in the first place.
This functionality will enter the public preview phase in September, and we will get a better look at how this is implemented, and how it can be tuned. The end result may be a walled garden inside our firewall that does not get crawled and has to be searched separately.
Last week I looked at the topic of encouraging innovation, with a focus from a leadership position. The truth is that each of us within a corporate team can bring about innovative change, and this is the notion behind intrapreneurship. Braden Kelley, in his recent article “Innovation: A Team Sport,” highlighted a problem that exists that isn’t often talked about – the fact that team members are often looked at as interchangeable. The truth is, everyone is different in their skills, capabilities and desires. And it is these differences that typically make teams stronger. Just look at The Avengers!
Your teammates on your school projects or in your day jobs are just as different from you as Thor is from The Hulk. Take one away and the team is not as strong. But the spreadsheets where headcount decisions are made do not show that. In fact, you can plop a new human in Excel’s C28 for half the cost if you go 1/4 of the way around the world to hire them. Never mind that the communication costs will be twice as much. You see, humans are not commodities like gold and money. They are valuable stocks with different capabilities and potentials. As a teammate or manager, you must leverage these different capabilities to move ahead.
That, my friends, is the beauty of intrapreneurship. An entrepreneur gambles his life savings on an idea attached to a hope or a dream. The intrapreneur rides on that wave with the resources at his/her disposal and tries to take them all to new heights. No one is asking you to invent the next light bulb. But given the resources you have, what novel approach to combining them will create something new and valuable?
I recently read Gartner’s report, “New CIO Responsibilities in a Digital Business World“, and was intrigued by their encouragement to nourish the “three subcultures within IT”. They defined these subcultures as:
- Operator (linear IT) — focused on keeping things running and improving, based on defined requirements where the priority is stability and reliability
- Innovator (nonlinear IT) — focused on creating new business value and capabilities where the need for speed, innovation and exploring fuzzy requirements are valued
- Guardian (leadership) — focused on ensuring the long-term success of the business, staying industrial strength while being ready for the future, balancing innovation with risk, ensuring a strategic long-term focus and investing in the capabilities required for the future
The standout in this list is the call out of “innovator” as a group that is focused on exploring the areas where a lot of ambiguity exists and is valued. Innovation is getting a lot of play in the IT field, but it is also getting stifled by the frameworks for risk reduction that IT values so much. Old school and new school companies alike including AT&T, Adobe, and LinkedIN are establishing new organizational models to encourage innovation via both financial empowerment and political empowerment. This suggests that innovation is not possible at the rate desired within the other two subcultures, operations and leadership.
Like many problems in this space, I believe it is a problem of structure. I also believe there are many structures that would succeed that do not result in a completely external group being formed. Google and other companies made famous in the last decade their application of 20% time — that is, 1/5 of the work week is designated to personally identified projects and the other 4 are dedicated to the initiatives that have been assigned. The problem here is that if you are within an operations group, much of your time is dictated by external forces, not planned project work. The line is further blurred when you look at DevOps groups that are responsible for new development as well as ongoing operational support.
There is not a one-size-fits-all response to encourage innovation. Organizations are going to have to look at their internal structures, their industry, and all the forces being placed on those walls to determine how best to respond. But they must not overlook their existing talent, and should find ways to include them in the innovation process (ideation, gate reviews, etc.) even if they cannot be dedicated full time. At the same time, the existing talent must be open to new ideas, products and methods that may run counter to “the way we’ve always done things.”
This month hasn’t been the worst ever, but it has been trying. I came down with the flu-like-crud on December 1st. This rendered my attempts to train futile. I think I’ve logged a single, solitary run this month. It took 3 weeks to recover. I had hoped that during this time my shoulder would recover. I injured it back at the end of October, and I’m not really sure HOW. Sadly it did not improve.
I went to the doctor today and the good news is that the x-rays and examination did not prove to be remarkable. The bad news is that it still hurts! The doc gave me a cortisone shot along with prescriptions for an anti-inflammatory and physical therapy. I start the medication today and will go to PT on Monday. Hopefully this course of action will yield results where my previous plan of limiting use did not. My next IM is not that far out in the future!