Developers: it's time to take back decision making, using data!

codesidekick

 

Ever sat in front of the screen wondering why it is you're doing what you're doing. No not the technical part, not the architecture stuff, but actually why you're even writing the code that you're writing? Who is going to see this feature, is it the right thing to build? Do you know off the top of your head how many daily or monthly visitors the website you're working on has? What about the actual feature you're working on? You're not alone.

Sharing data in organisations has the ability to empower everybody to make decisions, from intern to CEO. It gives meaning to the work we build and gives us the ability to test new and better ideas. It also means taking away some of that sweet power away from the decision makers and managers in our organisation and spreading it around.

At Rome2rio we've successfully run split test experiments where everybody's been encouraged to submit an idea and guess what ... the best ideas weren't the best because they came from the most experienced or most senior members of the team. They often come from the least likely of sources.

In this session we'll see real life examples of when developers were empowered to make product decisions and the awesome things that happened. And, of course, there’ll be a few war stories of when things didn’t go so well. We'll explore some tools like Google Analytics and show you how you can get your whole team running experiments on your Drupal site.

Session Track

Being Human

Experience Level

Advanced

Drupal Version