+ Follow

Execute for Every Screen

by shoobe01 on May 17, 2012

1,300 views

There are several ways that current development processes can miserably fail users and the business when trying to launch your project on multiple platforms. Massive changes, blame, or simply not ...

There are several ways that current development processes can miserably fail users and the business when trying to launch your project on multiple platforms. Massive changes, blame, or simply not understanding your missed opportunities, are the usual results.

The answer is not any of these, and certainly not to try to impose a new process. Instead, encompass all the existing processes to create a new philosophy of implementation. Avoid pitfalls and gaps, and play to the strengths of your team to operationalize a functional design and development processes.

Steven will talk about methods he's devised and used with business, analysts, and developers that make everyone happy and help assure projects actually launch.

Presented at D2WC in Kansas City on 17 March 2012

Accessibility

View text version

Upload Details

Uploaded via SlideShare as Microsoft PowerPoint

Usage Rights

File a copyright complaint

3 Embeds 882

http://floatlearning.com	880
http://www.linkedin.com	1
http://sandbox.clipboard.com	1

Statistics

Likes: 0
Downloads: 3
Comments: 0
Embed Views: 882
Views on SlideShare: 418
Total Views: 1,300

Execute for Every Screen Presentation Transcript

Executing forEvery ScreenEmbracing everyone’s limits toexpose you project’s strengths@shoobe01 #d2wc 1

UX thinks: Developers think:Principle of Most Time: Every product we buildThe most elegant and is a product we buildsimple solution to any for ourselves to solvedesign problem will be our own the one that requires problems…making the most developer decisions based on effort. real opinions trumps making decisions based on imaginary opinions. 2

No more hand waves 3

Shared principles• Modular• Iterative• Incremental• Patterns and best practices 4

ModularImplementation: User Experience:Good programming principles We don’t draw every page and(whichever you embrace) state independently, but considerencourage re-use, consistent the design holistically, and drawnaming and resource many items to be used acrossallocation, and using the simplest the product.solution.Re-usable components make work quicker and more efficient, morerepeatable, easier to understand for regular teams and easier toimprove or fix. 5

Iterative Implementation: User Experience: Start simple, learn as you go Review designs internally, with from both solutions and needs of user research and by analytics the customer/client, and build when launched. Identify, learn improvements on what you build and improve, on small and large before. timescales.Whether week two or release two, work is never thrown away, butimproved on and expanded to become better and more capable. 6

IncrementalImplementation: User Experience:Assigning developers one task Conceive holistically, but designhelps focus, and allows the team in easy-to-manage chunks. Splitand management to track the work to who can bestprogress, and further split (or perform the work, and deliver incombine) work as needed. pieces if needed for speed.Resources – both people and time – are limited. Deliberately breakup work in an ordered manner for management, and coordination. 7

Patterns & Best Practices Implementation: User Experience: Apply existing knowledge and re- Speeds work and constrains the use known good solutions, but problem space with , extend and combine to meet libraries, patterns and stencils. the system needs and project Analyzes or researches to find goals. the best solution.All of our work builds on history, knowledge and evidence.But watch out for best vs. common practices. 8

Coordinate to collaborate 9

Planning for multiple platforms 10

There’s no time• There’s plenty of time• Scale the engagement• It pays off in the end 11

Design for every screen• Gather information• Design for users, tasks, and goals• Make n assumptions about single technologies, interfaces or platforms• Create a blueprint of the whole service… then branch out• Design to target (end goal) experiences 12

Constraints 13

Development scales well 14

But the core team… 15

But the holistic team… 16

Blueprint 17

Branch design to each platform 18

Serial 19

Parallel 20

Staggered 21

Operationalize your process 22

Steven Hoobersteven@4ourth.com+1 816 210 0455@shoobe01shoobe01 on:www.4ourth.com 23