Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
This is a team sport
Search
Matt Jukes
June 20, 2018
Business
530
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
This is a team sport
New version of talk for New Zealand June 2018.
Matt Jukes
June 20, 2018
More Decks by Matt Jukes
See All by Matt Jukes
Roadmaps and Missions for the Scottish Digital Academy
jukesie
0
1.3k
A ChatGTP Christmas Quiz
jukesie
0
410
Jukes - User Manual
jukesie
0
160
my adidas
jukesie
1
450
Working in the open works
jukesie
1
76
Digital is a team sport
jukesie
0
640
The importance of being open
jukesie
1
96
The Wrong Users?
jukesie
0
640
Statistically significant taxonomy
jukesie
0
140
Other Decks in Business
See All in Business
どうせなら「楽しい仕事」をする
kozotaira
0
310
データを使う側視点のデータ整備 / 第2回 データ整備を前向きに考える会
shinu
PRO
0
270
事業領域
daisan123
0
470
己のキャリアと野望を語る ~はじめて出したCfPを供養しよう~
r5ni4
0
250
顧客理解レースでAIの一歩先を行く / Know customers better than AI
hirokiyamamoto14
PRO
1
450
NEXERA inc. | Company Deck
nexera
0
25k
株式会社ナビタイムジャパン 会社紹介資料2026
navitimejapan
PRO
1
2.3k
PM Kansai#5 Sponsor Session
y0suke4mano
0
210
TableCheck Inc. - Company Profile
tablecheckac
0
520
AWSのログ/アラートの調査を AIで自動化してみた話
tomomasa
0
150
キャンバスエッジ株式会社 会社説明資料
canvasedge
0
19k
なぜデベロッパーアドボカシーが必要なのか?
taiponrock
PRO
0
160
Featured
See All Featured
Producing Creativity
orderedlist
PRO
348
41k
Why You Should Never Use an ORM
jnunemaker
PRO
61
10k
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
2
500
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
287
14k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
6.1k
Git: the NoSQL Database
bkeepers
PRO
432
67k
Tips & Tricks on How to Get Your First Job In Tech
honzajavorek
1
720
Building the Perfect Custom Keyboard
takai
2
860
Building Flexible Design Systems
yeseniaperezcruz
330
41k
How to Think Like a Performance Engineer
csswizardry
28
2.8k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
123
22k
Believing is Seeing
oripsolob
1
210
Transcript
None
once (and future) civil servant current consultant serial leaper from
frying pan to fire
None
None
None
None
None
None
None
This is my truth.
None
I can tell you I don't have money, but what
I do have are a very particular set of skills. Skills I have acquired over a very long career.
2. Hiring 3. Culture 1. Context 4. Questions
2. Hiring 3. Culture 1. Context 4. Questions
None
This is for everyone.
It’s not OK not to understand the internet anymore.
Some of you..are working right now on another app for
people to share pictures of food or a social network for dogs. I am here to tell you that your country has a better use for your talents.
In 2011 the Government Digital Service (GDS) was founded.
GDS implemented spend controls on all digital projects..
..and introduced the ‘Service Standard’ against which all projects would
be assessed.
..and so our story begins.
@jukesie
2. Hiring 3. Culture 1. Context 4. Questions
None
The biggest digital transformation challenge is people not technology.
Hiring the best is your most important task.
Leave the rockstars to Homegrown.
Research your job titles. Don’t get cute. Don’t be clever.
Do be clear. Do be honest.
A/B test the job titles. Use free job boards, social
media and mailing lists and track which work best.
Write real job descriptions. Get people doing the jobs to
help. It is OK to be aspirational but don’t ask for the world.
Test your job descriptions better-job-adverts.herokuapp.com/about
Ask the community for help. Draft job descriptions on Hackpad.
Twitter polls on job titles. Feedback on interview processes.
Make the case for joining. Job descriptions are not enough.
Write blogposts, speak at meetups, sponsor unconferences.
None
Play to your strengths. If you can’t compete on salary
talk about other benefits. Not the foosball or the game nights. The challenge. The mission. The team.
Tap into your network. You are probably only one or
two degrees of separation from the best candidate. Build and nurture networks.
Tap into your network. You are probably only one or
two degrees of separation from the best candidate. Build and nurture networks.
Do it but be careful. Monoculture is worse than no
culture.
None
If you post it they will (not) come
None
The internet of public service. jo n l er
Take interviews seriously. Use consistent questions. Never interview alone. Agree
with other interviewer what you are looking for in a successful candidate. Specialist interviewers for specialist roles.
Be willing to wait. There is often pressure to fill
a vacancy. Waiting for the right candidate rather than the available candidate saves time in the long run.
..but once you find the right person you have to
move fast.
It doesn’t end at the interview. Give useful feedback to
unsuccessful candidates. Keep communicating with the successful candidate. Just sending an offer email and a start date is not enough
Introductions over induction. Plan the first week or two for
any new hire carefully with a mix of the mundane and the interesting. Don’t overwhelm them but get them involved asap. Make them feel welcome and wanted.
2. Hiring 3. Culture 1. Context 4. Questions
Culture eats strategy for breakfast.
None
None
Culture isn’t imposed it emerges. You cannot create a positive
culture by top down edict. It can be aspirational and ambitious but it emerges from behaviours already existing.
Have the team prepare principles. Encourage the team(s) to come
up with principles to work towards. Then reinforce them by making them a part of how you work every day.
Culture is more than posters on walls…but visibility is vital.
The details matter. Make sure people have the hardware and
software they need to do their jobs. Make training available. Give staff time to experiment and learn.
The environment is important. Seat the team together. Speak to
the team about desk layout if possible. Walls, walls, walls. Quiet spaces. Meeting rooms.
One remote. All remote. Team work is harder in remote
teams but also has benefits. Use the tools. Over communicate. Schedule time with colleagues. Read the 18F guidance.
The maker vs manager schedule. If you haven’t read this
and work in a team with designers, developers & managers —> http://www.paulgraham.com/makersschedule.html
Trust the team to make decisions. It is easy to
talk about empowering staff but you have to 100% follow through. Read ‘Turn the Ship Around’ about the leader/leader approach.
Leaders need to be umbrellas. You have to protect the
team from the HiPPO sh*t. Give them the space to do the work but don’t isolate them. Often their opinions will carry the most weight.
None
Corporate subcultures are hard. You can spend time building a
team culture but your wider organisation has a culture of its own and they may not coexist comfortably.
Culture can be fragile. Especially in the early days. You
have to be careful not to damage it with poor behaviours or bad decisions.
None
I don't know about you people, but I don't want
to live in a world where someone else makes the world a better place better than we do. Gavin Belson, founder of Hooli
2. Hiring 3. Culture 1. Context 4. Questions
Thanks.
Open Lab Friday 4-5 191 Thorndon Quay