Dan PInk: The Puzzle of Motivation
Sometimes people don’t really need incentives in forms of reward to work. I find myself doing things because they are things that interests me. The satisfaction of doing something meaningful and having the freedom to create is what invokes great productivity. Another great talk. Watch it!
There is a mismatch between what science knows and what business does. And what worries me, as we stand here in the rubble of the economic collapse, is that too many organizations are making their decisions, their policies about talent and people, based on assumptions that are outdated, unexamined, and rooted more in folklore than in science. And if we really want to get out of this economic mess, and if we really want high performance on those definitional tasks of the 21st century, the solution is not to do more of the wrong things, to entice people with a sweeter carrot, or threaten them with a sharper stick. We need a whole new approach.
And the good news about all of this is that the scientists who’ve been studying motivation have given us this new approach. It’s an approach built much more around intrinsic motivation. Around the desire to do things because they matter, because we like it, because they’re interesting, because they are part of something important. And to my mind, that new operating system for our businesses revolves around three elements: autonomy, mastery and purpose. Autonomy: the urge to direct our own lives. Mastery: the desire to get better and better at something that matters. Purpose: the yearning to do what we do in the service of something larger than ourselves. These are the building blocks of an entirely new operating system for our businesses.
Simon Sinek: How Great Leaders Inspire Action
As much as the title suggests Leaders to Team Members, I think this is also applicable in exploring avenues to reach out to the community in general. In how we can gain user confidence and loyalty. Great talk and indeed inspiring!
"Why? How? What? This little idea explains why some organizations and some leaders are able to inspire where others aren’t. Let me define the terms really quickly. Every single person, every single organization on the planet knows what they do, 100 percent. Some know how they do it, whether you call it your differentiated value proposition or your proprietary process or your USP. But very, very few people or organizations know why they do what they do. And by “why” I don’t mean “to make a profit.” That’s a result. It’s always a result. By “why,” I mean: What’s your purpose? What’s your cause? What’s your belief? Why does your organization exist? Why do you get out of bed in the morning? And why should anyone care? Well, as a result, the way we think, the way we act, the way we communicate is from the outside in. It’s obvious. We go from the clearest thing to the fuzziest thing. But the inspired leaders and the inspired organizations — regardless of their size, regardless of their industry — all think, act and communicate from the inside out.”
How to Conduct Your Own Google Venture Design Sprint
Day 1: Understand
Dig into the design problem through research, competitive review, and strategy exercises.
Day 2: Diverge
Rapidly develop as many solutions as possible.
Day 3: Decide
Choose the best ideas and hammer out a user story.
Day 4: Prototype
Build something quick and dirty that can be shown to users.
Day 5: Validate
Show the prototype to real humans (in other words, people outside your company) and learn what works and what doesn’t work.
Wi-Fi Based Gesture Recognition Technology #innovative
Designing the zoom feature of FiftyThree’s Paper app
- Draw On Previous Experience and Understanding– The biggest problem is startups in search of a problem. Chase what you’re passionate about; you’ll probably already have knowledge in the space.
- Have A Hypothesis About How You’re Different– Have a point of view about your startup. Why is there a special opportunity for this now?
- Never Build Without Sketching– Mike says he and Instagram co-founder Kevin Systrom would go to a cafe with little iPhone design pads where “we’d build and throw away entire features. You’d waste three or four pieces of paper, not three weeks of coding.”
- Learn In Weeklong Increments– Start with a question: “Will folks want to share photos on the go? Can we build filters that look good?” Spend the week investigating, and by Friday have a conclusion and move on.
- Validate In Social Situations– “We called this the Bar Exam. If you can’t explain it to the guy or girl at the bar, you need to simplify.” Don’t just test with your techy friends.
- Know When It’s Time To Move On– “I know ‘pivot’ has become a dirty word, but if there’s no unanswered questions left, then it’s time to move on.”
- The Wizard Of Oz Techniques For Social Prototyping– You don’t need to build everything at first. You can be the man behind the curtain. Krieger says him and Systrom tested an early version of a feature which would notify you when friends joined the service. Instead of building it out, they manually sent people notifications “like a human bot” saying ‘your friend has joined.’ It turned out not to be useful. “We wrote zero lines of Python, so we had zero lines to throw away.”
- Build And Maintain A Constant Stream Of Communication With Your Audience– Don’t spend months building something without any idea if someone actually wants it.
The Reddit Story
Jack Dorsey’s Stanford Talk
Carrier Status bar - 320x20
UIView - 320x460
UINavigationBar - 320x44
UITabBar - 320x49
UISearchBar - 320x44
UIToolBar - 320x44
UIPickerView - 320x216
UIDatePicker - 320x216
UIKeyboard - 320x216
UISegmentedControl - 320x44
UITextField - xx37
UISlider - xx23
UIActivityIndicatorView - 37x37
UIPageControl - 38x36
Hello World was the very first program that I wrote in my C++ class during college. I thought that this would also be the best title of my first blog entry on Tumblr. Ever since a young age, I always had been a dreamer. I used to watch this anime titled Voltron and Daimos. I was so fascinated and wanted to become an engineer, scientist, and inventor. In my mind, I wanted to build one of those humongous robots. Fast forward to the future, I still had that sense of fascination with technology. I wanted to become both and engineer and doctor, which were quite different. My desire to become both was not to complement each other but just to be both. I did end up starting my pre-med classes. However, due to situations beyond my control, I ended up taking computer engineering.
I learned a lot, and my day-dreaming progressed. I was introduced to Mac OS X and Apple computers; I fell in love with them. I loved how beautiful they are and at the same time very functional. Ideas kept sprawling up in my head. The iPhone was introduced, and that moment was amazing. The ideas in my head exponentially grew.
Not until recently have I had the real intense desire to just do it. The talk by Jack Dorsey at Stanford was one of the stimuli for me to just go and do it. He mentioned in the talk that he had ideas, and he had to get it out of his head to see it on a surface that is not the mind. (You can watch the whole talk here: http://ecorner.stanford.edu/author/jack_dorsey) This blog is my way of doing that. I am not sure what the content of this blog will be but I hope it would be of help to someone, someday.