The real thing with Agile is that never ends. From the moment of your first very rough conceptual prototype to the moment that you ship code you can sell you’re testing all the way through. You’re checking with your customer all the way through. That’s the end state that we’re working towards with our clients is the point where you don’t even have to wait for working code to do the iterations with your customers.
El buen diseño no sólo acabará con los manuales de usuario y las instrucciones de uso, sino que construirá nuevos modelos de comunicación basados en el aprendizaje por interacción y la expresión creativa.
Practice Fusion, the leading provider of health records software for medical professionals, has published a nice recap of their user conference, Connect11, where Alan Cooper spoke about the role of interaction design in health care. Among the questions answered – “what do you get when you cross a computer with a doctor’s office?”
At the 13 minute mark, Stefan Klocek presents a prototype of Practice Fusion’s new iPad app.
Via Cooper Journal
What we read from blogs we’re subscribed to it’s part of our every-day inspiration.
After a year, I’ve had opportunity to read and discover different posts with a special influence in me, anyhow. The year is ending now and this is the summary of the readings I recommend before 2012.
- 100 preguntas para entusiastas del diseño
- how to design multi-device user experiences
- Cutting Room Floor
- How to design a mobile responsive website
- Design studio and agile UX process and pitfalls
- Wood-voice recorder.html
- Homofobia en Twitter tras el debate electoral
- Vision del futuro by Microsoft
- Reducing unintended consequences of Electronic Health Records
- Materiales UX evaluacion de la usabilidad
- Nueva propuesta de iconos gestuales
- Aplicaciones para el iPad: ¿web-app o iOS-app?
- Ccordero con verduras al horno
- Pattern sheet
- Yahoo visualizes real-time email statistics
- CreativeMornings Video: Jason Fried
- Nine presentations about device UI
- Hierarchy of digital distractions @MOMA
- Myers brings personality types of designers
- 4 things no-one told me about high-fidelity wireframes
- Sirius: nuevo sistema para la evaluacion
- Aarquitectura de informacion: fundamentos
- Effective minimalism in experience design
- The Neuromarketer
- Now online:open IxD thesis presentations
- Evaluating UX by measuring task efficiency
- Hi I’m a UX developer, you’re a what?
- 50 reasons not to use Photoshop for web design
- Topical influence
- Mi Twitter es también de mi empresa
- 4 quick tips for getting the most out of google analytics
- Frase del guru: derechos de autor
- Effective developer experience
- Considerations for mobile design, part 3: behavior
- Lo que no se dice sobre el supuesto “milagro alemán”
- Mobile form design strategies
- A Guide to Writing and Designing Easy-to-Use Health Web Sites
- Dime tu correo electrónico y te diré quién eres
- Diseñadores que creen en si mismos
- Medir la experiencia de usuario en la nube
- BSchool nos añade a su lista de 20 blogs sobre el cerebro
- Considerations for mobile design (part 1): speed
- What we need are personal
- Top 6 help design patterns for iphone apps
- El precio de la usabilidad en los formularios
- Comprehensive mobile UX presentation
- The 26 books that made me an Interaction Designer
- I love UXdesign
- Book review The design of design essays from a computer scientist
- When Bbraun stopped being braun
- El teléfono más simple del mundo
- Design Criticism and the Creative Process
- The Future of User Interaction
- The Power of Comparison: How It Affects Decision Making
- De Harvard University a “Google University”
- Following the example of Angry Birds
- To me, design is…
It takes almost as much creativity to understand a good idea, as to have it in the first place
Design is compromise
I’ll share with you an interesting reflection found in the book “Prototyping” by Todd Zaki Warfel regarding why we don’t expect prototyping as stage in the process in software development, regardeless the myth of the “return of investment”:
I think the first reason is that in software development, the emphasis is often placed on the development process and not the design process. The industry doesn’t call it “software design”; they call it “software development.“
In software development, design is often an afterthought. The emphasis is on the technology or features—not the design. In architecture and industrial design, however, the emphasis is on design. Form follows function.
Another reason is that software development is seen as a manufacturing process, but architecture and industrial design are seen as a craft.
In the following pages we’re introduced to the concept of Design studio, which is very common in other design fields:
In studio classes, you design or prototype and present to your peers. Your peers critique your work, highlighting the strengths and areas that still need some work.
Prototypes are not just a tool to communicate or to describe ideas, but also a work methodology, a phylosophy where sharing, colaborating and criticizing can speed up the process, prevent future failures and empower peers into trust and success.
It’s not a believe, fortunately I could check it by my own in my short experience, so the answer from my viewpoint is clear:”Yes, the software industry must learn a lot from other fields and design can help to lead that subversion”.
To build a persona can be tricky; you can just look how actors need months to put in the shoes of a their new characters. In UI design, personas’ creation is part of the analysis stage: they will be used to define requirements, to prepare user tests, to support decisions and to establish a meeting points between designers, developers, and stakeholders.
What is a persona?
Personas are fictitious users you create based on your user research. Personas summarize your user research findings and provide a practical approach to understanding the requirements of your target audience and keeping user perspectives in mind when designing products and creating documentation for them.
By Niranjan Jahagirdar and Arun Joseph Martin for UX Matters.
I wanted to include this definition just as an introduction, because what matters to me now is how to perform personas’ research when you cannot access to any focus group, you cannot do direct interviews or observe users.
Beyond the discussion about whether this artifact is useful or not, I think that even for large organizations is a wothwhile investigation which will help to the team to be closer to the real and target user. So, this is basically my suggestions whenever you need to face a persona’s modeling:
- Identify primary and secondary individuals to give importance to product requirements
- Identify behavioural variables and patterns by reading blogs, analysing the professional/gender/demographics statistics associated, and understanding the complexity of their tasks beyond the technology
- Undestand how business rules, and work environment can affect to the performance and frequency of their tasks
- Learn how subjects like politics can affect to the user daily work (tasks, goals, attitudes and motivations)
Tips from above are not new, you can find more precise ones in the Chapter 5: Modeling Users: Personas and Goals, of the book About Face 3.
Creating persona’s is not an obscure or expensive procedure but a powerful tool wich will help designers to make decisions confidientially.