Simon Sinek

Profit isn't a purpose, it's a result. To have purpose means things we do are of real value to others.

Good business

Good business

Good business

Good business

Good business

Good business

Good business

Good business

Good business

Good business

Design thinking

If you understand people better it's easy to create relevant value for people

Ash Maurya

The Lean Startup

Open source software is software that can be freely used, changed, and shared (in modified or unmodified form) by anyone.

open source

• Transparent
• Anyone can get involved and help out
• Self-organising
• Highly collaborative
• Empowering

Erica Joy Baker

ex-Google

open source principles are inclusive and favour diversity

closed source

• Information is hidden from people unless they have the right clearance levels
• Silos form because of information hoarding
• Organisational inefficiencies and doubling up
• More political
• Lots of management required
• Old processes become meaningless

open source

• Information is available to anyone who wants to know about it
• Teams are all working towards the same goal
• High availability of information leads to increased efficiencies
• Highly collaborative and innovative
• Self-managing or managed by process
• Processes are continually updated by the team

systems thinking

the reactive manifesto

• Responsive
• Resilient
• Elastic
• Message-driven

www.reactivemanifesto.org

responsive

The system responds in a timely manner.

Agile companies can shift their processes to respond to changing market demands. Companies that can adapt and handle change well have an advantage over slower-moving competitors. 

Resilient

The system stays responsive in the face of failure. Resilience is achieved by replication, containment, isolation and delegation.

• Replication: knowledge management
• Isolation and Containment: Remote working, fewer meetings
• Delegation: hire people you trust, four minute management

ELASTIC

The system stays responsive under varying workload.

Uber's approach to supply and demand fluctuations means that surge pricing is automatically triggered at certain supply/demand combinations which brings out more workers.

MESSAGE-DRIVEN

Reactive Systems rely on asynchronous message-passing to establish a boundary between components that ensures loose coupling, isolation and location transparency.

Think Slack and emails rather than conference calls and meetings. Asynchronous messaging doesn't interrupt, enables offsite work and helps with accountability.

Back-pressure

When one component is struggling to keep up the system as a whole needs to respond in a sensible way.
It is unacceptable for the component under stress to fail catastrophically or to drop messages in an uncontrolled fashion.

Cross-functional teams

google design sprints

A key feature of their methodology is to include at least 7 people from the company from different departments.

Teams solve problems better when they don't all think the same way.

usability

(for your code)

Jakob Nielsen and Don Norman

The Nielsen Norman Group

It’s harder to read code than to write it.

Joel Spolsky, CEO Stack Exchange, co-founder of Trello

10 usability heuristics (for your codebase)

• Visibility of system status 
• Match between system and the real world 
• User control and freedom 
• Consistency and standards 
• Error prevention 
• Recognition rather than recall 
• Flexibility and efficiency of use 
• Aesthetic and minimalist design 
• Help users recognize, diagnose, and recover from errors 
• Help and documentation

no engineer is an island

• Coding is about collaboration
• Mostly we work in teams, because more brains make things higher quality
• Even if you work on your own, you may one day leave and hand over to someone else
• The best code is both most efficient/elegant and easily understandable/usable

theory of constraints

Dr. Eliyahu Goldratt

Author of The Goal

How it can work

• Chart out your planning, design, development and testing workflow and create metrics around each stage
• Find out where your team is "blocked" and where "inventory is building up"
• Unblock that constraint and then work on the next one

Research

Design

Dev

Peer review

Automated

testing

Blocked!

TEST-driven development

Not test-driven development

• Decide to build something
• Build the thing
• Later on, build another thing, and break the original thing
• Catastrophe

test-driven development

• Decide to build something
• Write a test that fails until you build the thing
• Build the thing
• Test passes! 
• Later on, when things are built, they can't be shipped unless all tests pass.

usability testing

Designers already do some testing, usually usability  testing.

But usability testing often comes late in the process, and sometimes is an "added bonus", or just a way to prove existing assumptions.

test driven design

Test driven design uses usability tests, analytics measurements or other forms of benchmarking as a pre-requisite to design tasks and improvements.

Focus on measurement helps design teams better judge whether they are providing real value.

simple made easy

Rich Hickey

Creator of Clojure

simple

(vs complex)

• One role, one task, one concept, one dimension
• Not interleaved or interwoven with other things
• Can be split out and used on its on

easy

(vs hard)

• Near, at hand
  • On the hard drive, already in the toolset
• Near to our understanding/skill set
  • Familiar
  • Near our capabilities

Why do this...

When you could just do this?

EASY (Photoshop)

• I have done it this way before
• I have Photoshop on my computer already
• The stakeholders like PSDs and it makes it easier to explain stuff to them
• I can't communicate my idea as easily in a style guide
• I don't know how to code

simple (Pattern library)

• Design time is focused on components, which are reusable, rather than once-off PSDs
• Design effort pays off over time
• Consistency increases across the whole project
• Team is empowered to do things without getting blocked at design stage

JOBS TO BE DONE

Harvard Business School, author of The Innovator's Dilemma

Clayton Christensen

Customers Don't Simply Buy Products -- They Hire Them to do jobs.

Clayton Christensen

Design is more than just pretty pictures

• Understanding the competition
• Shaping the roadmap
• Design things that engineers can build
• Evaluate designs in real time usage
• Throw away ideas - design the the thing right, but also design the right thing.

The 25 5 rule

Warren Buffett

One of the most successful investors in the world

list 25 things you want to achieve

choose your top 5

never think about the other 20 ever again

Minimalism is not subtraction for the sake of subtraction, minimalism is subtraction for the sake of focus.

Designer?
ENGINEER?
MANAGER?

THANKYOU!

@meelijane