Let me go out on a limb and say "probably not"… buy why not? Simple right… a Toddler just learned to walk and probably just started running somewhat clumsily. It would be a totally unrealistic expectation to expect your toddler to then be able to run a "Marathon".
But often in our organizations we set these type of goals without understanding the path and dependencies required to reach the goal.. we try to go from "crawling" to "running" and forget we don't know how to "walk" or even worse we proclaim we are going to run a marathon..
Back to the example, so what are some levels of maturity and their order for Humans:
Maturity Levels: Infant, Toddler, Child, Adolescent, Adult, Senior
Now there are also probably some dependencies and capabilities between the levels. For example, an Infant doesn't have the capability to be "Independent" they are in contrast "Dependent" their capabilities are fairly limited they eat, sleep, pee, poop and have basic communication skills (cry or silence)… anyhow so the point which I hope is obvious is that over time as the Infant "Matures" through the various levels they are "capable" of more and more. Also each level usually has dependencies around things being "mastered or accomplished" in the previous levels.
Just as we don't expect our 4 year olds to bring home an Income we shouldn't have similar unrealistic expectations in our business, technology, architectures, organization and processes. I'm not saying don't have "bold goals" or "grand visions" (both favorites of mine personally) but my point is in order to accomplish things you have to work on understanding where you are currently at (Maturity level) and the the path and dependencies to move forward and reach success.
Although it seems obvious.. next time you have that project that just seems to never go away.. or is struggling to make progress.
Take a step back.. and make sure your not trying to run before you can walk.
I received a funny email from one of my co-workers with the subject “Failing a Test with Dignity” it had a bunch of images like the two below which were my favorites.
Anyhow, I found the email very amusing.. but in all seriousness it also reminded me of a belief I have. That there is much Value in individuals who are creative, imaginative and are risk takers. Now maybe, the students below were just trying to be “funny” in creative ways but being “funny” can also be risky.
A little old but still relevant:
2. Instant Utility
3. Software is Media
4. Less is More
5. Make it Programmable
6. Make it Personal
I agree with them all it is a great list I would call 5.) Platform First… but I guess “Make it programmable” is a little easier to understand.
There is a question at the end of the video about Mobile.. however, I really think that once your app is “Programmable” then the types of devices it can be consumed on is really limitless. However, there are some Mobile qualities that could be useful like being “Location Aware” although not sure if it would qualify at a generic principle level.
One I would stick in there is “Play well with others” specifically in regards to Authentication, Authorization and User Data via the leverage/support of emerging/standards like OpenID, OAuth, OpenSocial, FaceBook Connect etc… What do you think is missing ?
I was recently reminded of an old Seth Godin post I liked entitled, ”When you stand for something” check it out.
The point of this post isn’t about how to be Authentic and certainly it’s not about being fake.
It is about being:
Genuine: free from hypocrisy or pretense
Being genuinely fake is a choice that is perfectly alright since your not purposely deceiving.
What I dislike the most is when something tries to be and is conveyed as Authentic but is not Genuinely Authentic. This can be people, processes, strategies, rules or products that are conveyed as authentic but clearly are not and everyone knows it.
One example would be a rule that is strictly enforced but not in all cases, but instead of being transparent as to why there are those cases folks simply pretend they don’t exist.