Skip to main content

Daniel Pink says we're doing it wrong

Daniel Pink claims science says we're doing it wrong in the Deloitte Digital studio model.
http://www.youtube.com/watch?v=rrkrvAUbU9Y

Currently within my office there is a formalized effort to find ways to improve our work culture. According to Pink, the organization needs to learn to support and reward the correct set of motivations. Based on his talk, one of the friction areas I see between studio consulting and financial consulting is that the bonus structure for financial consulting where mere effort and extra time linearly deliver incrementally better results works against you in the creative software and design work we do in the studios. Pink suggests if we want to adapt to what the decades of motivation research conclude, maybe we should talk about removing the consideration of performance-affected bonuses from the studio model entirely, just push the financial concern right off the table, and let people have the agency to act on the intrinsic motivations that made them worth hiring in the first place. Sure, all I'm backing this up with here is just a TED talk on Youtube, but the points about morale, turn-over, and productivity dropping when a performance-based reward system is imposed over creative work seem to align fairly well with experience so far. Food for thought...

Here's an even better version of the talk where he goes more in depth. I apologize for the crackling audio. It goes away after a bit.
http://www.youtube.com/watch?v=_mG-hhWL_ug

Comments

Popular posts from this blog

Jenkins + Devices + AndroidJUnitRunner

New Android build system and test runner, same goose chase using undocumented features and hacks

As I've posted before, I am a big fan of Jenkins. It is extremely flexible, open source, and supported by a staggering array of plugins actively developed by engineers running over 100,000 instances of the server worldwide. With it's distributed node model, you can even build your own device cloud for hosting enterprise-scale automation, economizing hardware investments by sharing resources across multiple projects as well as speeding up automation by parallelizing test runs. I had been using a Jenkins-based system in the past to support instrumentation automation with Robotium quite happily. For the last couple years however, my work hasn't required that as much and I've found myself doing a lot more manual testing and using UiAutomator which didn't require a tight integration between the product codebase and the test code. As a result, I've been slow to adopt the…

UiAutomator and Watchers: Adding Async Robustness to UI Automation

"I'm looking over your shoulder... only because I've got your back." ~ Stephen Colbert
After my recent UiAutomator review a user brought up an important question about the use of UiWatcher. The watchers serve as async guardians of the test flow, making sure the odd dialog window doesn't completely frustrate your tests. Having a tool that automatically watches your back when you're focused on the functional flow of your tests is awesome. 100% pure awesomesauce. Since the API documentation on watchers is scant and the UI Testing tutorial on the Android dev guide doesn't cover their use in depth, I figured I should add a post here that goes over a simple scenario demonstrating how to use this fundamentally important UI automation tool.

In my example code below, I'm using uiautomator to launch the API Demo app (meaning run this against an Emulator built in API level 17 - I used the Galaxy Nexus image included in the latest ADT and platform tools). The te…

Run-As Like the Wind: Getting private app data off non-rooted devices using adb run-as and a debuggable app

"You're some kind of big, fat, smart-bug aren't you?"
~Johnny Rico, Starship Troopers (1997) One of the most important things about writing bugs is making them descriptive but concise. Screenshots, video, debug logging, and hardware snapshots are all fairly standard or available to Android testers these days and can save you enormously on text when communicating what constitutes the bug. Sometimes though, the app gets into a weird state due to some transient data issue where you may not own the API or the complexity with forcing the app data into a certain state is prohibitively high. In those cases it is very handy to directly inspect the data the app has in its own directories.

Getting at this data is trivial on emulators and rooted devices but due to file system permissions, this data is otherwise completely private to the app itself. If you're like me, you tend to test using devices rather than emulators and you probably prefer not to root your devices since t…