Designing the Unknown - IA Konferenz Berlin 2013
Upcoming SlideShare
Loading in...5

Designing the Unknown - IA Konferenz Berlin 2013



Designing the Unknown - IA Konferenz Berlin May 3rd 2013

Designing the Unknown - IA Konferenz Berlin May 3rd 2013



Total Views
Views on SlideShare
Embed Views



6 Embeds 527 390 89 28 11 8 1



Upload Details

Uploaded via as Microsoft PowerPoint

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.

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

Designing the Unknown - IA Konferenz Berlin 2013 Designing the Unknown - IA Konferenz Berlin 2013 Presentation Transcript

  • Designing the unknownBogdan Stanciu@bog_danIA KonferenzBerlin, May 3rd, 2013
  • People > Process > Culture > Products
  • The products
  • The solutionsTalentManagementAcquireApplyHireOnboardManagePerformanceOffboardTrainPromoteWrite upUnempl.InterviewE-VerifyTax creditsScreenScheduleBackgroundcheckDo notrehire
  • The culture
  • The peopleTom IllmenseeUX directorChip TroutVD managerArchie MillerIxD managerChris BrownIxDSte GrainerIxDChris EklundIxDBridget WalshVDShannon SadyVDBogdan StanciuIA
  • 5xThe teamsCore Balanced
  • The processIf you cant describe whatyou are doing as a process,you dont know what youredoing.William Edwards Deming
  • The methodologyWaterfall AgileWaterfall Agile picture by Bruce Kenny © 2009Lean
  • What I learnedLack of consistent frameworks.Inconsistent processes.Unbalanced teams.
  • The misconceptionsSpeed over quality.No process.No documentation.Delivery over discovery.
  • The barriersSome resistance to change.Lack of consensus across and withinproduct teams.Incomplete understanding of UX.
  • You don’t create a culture.Culture happens. It’s the by-product of consistentbehavior.Jason Fried
  • What we wantedConsistent design process.Dialog between people and teams.Better quality in our work.
  • You rarely improve anorganization as a whole byimproving the performance ofone of its parts.Russell Ackoff
  • Designers don’t designanything. Organizationsdesign everything.Austin Govella
  • Lean framework
  • 1:1 Interviews
  • Critique
  • Card sort
  • UX process
  • Art resides in the quality ofdoing; process is not magic.Charles Eames
  • TestThinkMondayPersonasCharterScenariosMakeTuesdaySketchesDesign studioIAPrototypingCopyCheckWednesdayResearch planningSession facilitationQualitative analysisThink / MakeThursdayScenariosRevise prototypesVisual designCheckFridayResearch planningSession facilitationAnalysisCritiquePM
  • Core Team processIdeasDiscovery Design DeliveryProductsExperimentsbacklogProductbacklogOpportunitybacklog
  • Practice
  • Practice
  • Practice
  • Designer > Team > VP > CEOPromote
  • What you can doInterview your team.Map individual processes and critique them.Unify the findings and test the results.Share with your organization.
  • Who can do itAnyone.Teams of one.In-house teams.Agencies with their clients.
  • Why do it?Because you owe it to yourself and to thepeople who work with you.Because you want to know where you stand.Because you want to be prepared for thefuture.
  • People > Process > Culture > ProductsChangeagentsIgnitedialogLead withvisionRefinequality
  • Thanks toJan Jursa T-systemsJim Kalbach Citrix OnlineStephen Köver IA KonferenzAndreas Lange MediaworxWolf Noeding InterComponentWareLutz Schmitt Nexum
  • Thank you!bog_dan
  • CreditsCover photo office photos by Baskerville website design by Chip Trout and Bridget WalshSolutions flow by James BarettWaterfall Agile picture by Bruce Kenny © 2009Prototype photos by Tom IllmenseeStory map and personas by Archie Miller and Nick Jester