Commbank Internal Hackathon
Upcoming SlideShare
Loading in...5
×
 

Commbank Internal Hackathon

on

  • 395 views

My keynote slides from the internal hackathon at the Commonwealth Bank Australia.

My keynote slides from the internal hackathon at the Commonwealth Bank Australia.

Statistics

Views

Total Views
395
Views on SlideShare
394
Embed Views
1

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 1

http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Commbank Internal Hackathon Commbank Internal Hackathon Presentation Transcript

  • C B A H a c k a t h o n OPEN -SOURCE THINKING TOOLS IN DIGITAL PRODUCT DEVELOPMENT …in 15 minutes. ! READY?
  • 15 SECOND OVERVIEW FOR A 15 MINUTE TALK The things ■ A few things about projects ■ The Thinking Tools ■ When to use the tools ■ Leveraging other services ■ Doing it earlier in the process !2
  • PROJECT METHODOLOGIES ARE STRUCTURED FOR CONSOLIDATION BUT to solve the really tricky problems we need great divergent thinking at the appropriate times. !3
  • MISTAKE 1: WATERFALL IS SINGLE PASS. ! MISTAKE 2: REQUIREMENTS CAN BE GATHERED. Waterfall was originally designed to afford multiple passes, which would result in something pretty close to Agile. Requirements cannot be gathered - they must be found in customer insights, and subsequently validated. !4
  • Consolidation is an intrinsic and seemingly natural feature of any project. What is less natural is divergent thinking which leads to options. This is why an explicit tool for idea generation is important. !5 Catalyst for Variations/ Options Catalyst for Variations/ Options
  • SYNTHESIS DOESN’T JUST HAPPEN. Creativity isn’t magic. It can be an explicit process, applied when and where needed. !6
  • THE OPEN SOURCE THINKING TOOLS X10 ■ Multiply options by 10 ■ Works best when applied to a specific element/ metric/ perspective ■ Works extremely well with scale and relative proportions ■ Versions include: Divide by 10, adjacent 10, 10 parts etc. ■ Make up your own version ■ Resource: The X10 Memeplex. Book Download:https:// docs.google.com/file/d/0B44Jw1ES0js6cDJGekwwWmJhd28/edit? pli=1 ! ! ! !7
  • !8 X10 is ideal for early sketching stage where you need many design options to begin to articulate a vision.
  • THE OPEN SOURCE THINKING TOOLS Good, Bad, Better ■ Apply tool to any solution hypothesis. (not so great with customer problems) ■ Call out the GOOD - get it out there. ■ Call out the BAD - be strong, some of the best solutions come from here. ■ Transform the BAD into a better. ■ This method uses the momentum of previous work to drive forward positively. ! ! ! !9
  • !10 GBB is an excellent mechanism for generating quick iterations to a concept in a short period of time. Especially if working with a non- diverse team in a vacuum (like a Hackathon)
  • Consolidation is an intrinsic and seemingly natural feature of any project. What is less natural is divergent thinking which leads to options. This is why an explicit tool for idea generation is important. !11 Problem Definition Examples: Hypotheses Parallel Design Research A/B Testing Design Build GENERATION USER TESTING QA TESTING X10 GBB X10 GBB GENERATION
  • LEVERAGING EXISTING PLATFORMS Hypothesis Testing ■ Email first - just like mobile first. ■ Social first ■ Research platforms / javelin.com etc ■ Airtasker ■ Parallel design ■ A/B testing ! ! !12
  • ONLY FOOLS CODE FIRST Don’t build first here’s why: There are several types of risk that can kill your company here are a few (but are not limited to): ■ TEAM- are we the right people to execute? ■ MARKET - do people want to buy it? <usually the biggest risk ■ TECHNICAL - Can we build it? <Most hackers start here..oops!! ! Kareem Mayan ! ! FULL ARTICLE http://blog.reemer.com/why-only-fools-write-code-first ! ! !13
  • WHY WE CAN BE FOOLS TODAY It’s ok to build and validate because it’s a hackathon has the following benefits: ■ Safety in Numbers - Multiple groups provides multiple attempts at different ideas in parallel. This model is used in Seed funds. 1 success 9 failure - with pooled resources runs a profit. ■ Technology led innovation - new intersections of technology and ideas can give rise to fantastic new products which then find a market. Often not possible within the confines of a customer insight led development. ! !14
  • GET BACK TO WRITING CODE. !15
  • For questions or suggestions: ! Mike Biggs mbiggs@thoughtworks.com THANK YOU