For 50 years it’s been engineers in the drivers seat and designers in the back when it comes to software design. But with new technologies and ways of working perhaps it’s time for an entirely new kind of road trip. Join Indi Tansey (Chief Community Officer and co-founder of Codebots) and Jordie Peters (Senior UX designer at WorkingMouse) as they navigate the changing role of design in their industry and share their ideas for to getting designers behind the wheel in the development process.

1. Codebots.com
The future of software is
design-driven and
bot-powered.
Indi Tansey & Jordie Peters

2. Codebots.com
1. Indi and the old way
2. Jordie and the new way
3. The bot-powered future of work
4. Design-driven software & stories

3. Codebots.com
Hello humans.
I’m Indi.

4. Codebots.com

5. Codebots.com

6. Codebots.com
I’m Jordie.
First time meetup speaker.

7. Codebots.com

8. Codebots.com

9. Codebots.com

10. Codebots.com

11. Codebots.com

12. Codebots.com

13. Codebots.com

14. Codebots.com

15. Codebots.com
What does it mean to be
bot-powered?

16. Codebots.com
A Codebots
road trip.

18. Codebots.com
Bots that code +
humans that create.

19. Technology
with heart.
We can’t do it without you...

20. Codebots.com
What does design-driven
look like?

21. The Way of
Working
Broadly speaking, a project is
broken into five phases: Brief,
Scope, Development, Releases,
and Support.

22. Codebots.com
Squad
structure.
Project groups are referred to as
squads, which consist of two
project delivery teams known as
pods. The team members of each
squad are managed by a squad
lead.

23. Codebots.com

24. Codebots.com

25. Codebots.com
Agile design vs deep
discovery.

26. Codebots.com

27. Scope
The plan diverges at the
beginning during the discovery
phase to ensure all possible
solutions are considered, before
converging at the realisation
stage into with a solution that
feels provides the most value.

29. Codebots.com
Discovery
Interviews.
Have a chat with your users to
gain insights into what they need
and want. Identify pain points
with their current experiences.

30. User Journey.
Take the pain points you learnt
previously and begin to map out
an ideal journey that these users
would benefit from.

31. Codebots.com
Development.
The primary role of the designer
is to be the voice of the user
when they’re absent and ensure
development is on track with
scoping.

32. Implementation.
At the start of an iteration, Designers
can assist the Developers by providing
them with the page structure of
upcoming functionality.
Designers are responsible for creating
and maintaining a pattern library for
each project to create the look and feel
of the application.

33. Codebots.com
Case studies.

34. Codebots.com
Field Trials.
Exactly how much value does a codebot add?

35. Codebots.com
Chatbot.
The Codebots forms behaviour
was linked to a chat interface. That
interface had an API linking to the
participants CRM in order to verify a
users identity. Upon verification, the
user could request information relating
to their account. This was wrapped in
an iframe ready to be deployed on any
web page.

36. Codebots.com
Estimated time
without a codebot.
8.3 weeks Much faster (45%)
Faster (55%)
Similar (0%)
Codebots vs. regular
speed.
9.23 out of 10
Average customer
experience.

37. Codebots.com
SuzanneStays.
A boutique accommodation and
experience booking site, designed for
individuals who require assistive
technology in their daily lives.

38. Codebots.com

39. Codebots.com

40. Codebots.com

41. Codebots.com
The future
of work.
– Daniel Pink

42. After a good
read?
Get your copies at codebots.com

43. Codebots.com