Report
Share
Recommended
DesignMap (hearts) Prototyping
A talk about a recent project where we pivoted our design process. Using Sketch, InVision and a High Fidelity Prototype as a deliverable instead traditional PDFs.
Sixty Design Tools
An inventory of ~60 design tools, organized by JJGs Elements of Design. Includes types of feedback appropriate at each level, and for each tool the input and capabilities necessary and the output you can expect. Kind of a lego kit for designers!
Recommended
DesignMap (hearts) Prototyping
A talk about a recent project where we pivoted our design process. Using Sketch, InVision and a High Fidelity Prototype as a deliverable instead traditional PDFs.
Sixty Design Tools
An inventory of ~60 design tools, organized by JJGs Elements of Design. Includes types of feedback appropriate at each level, and for each tool the input and capabilities necessary and the output you can expect. Kind of a lego kit for designers!
Practice: Design "Swarms"
A quick talk on things we love: in this case, knitting while on phone calls (to "hack" the urge to multitask in a way that supports better focus), but most of the talk is on a new form of massively multi-designer brainstorming we're calling a "design swarm".
Design at Scale: A Storage Case Study
A case study of designing at scale for an enterprise client in the storage vertical. A review of what we mean by "Consumerization of the Enterprise." Do we mean designing IN or FOR enterprise?
And 4th order design: the enterprise system, managing and designing alongside a complex B2B sales channel, old-fashioned challenges with engineers, and reaching “customers”.
DesignMap (hearts) Slack
Learn why Slack is the medium of choice for ad-hoc synchronous and asynchronous conversation.
Enterprise is Sexy
Nathan Kendrick, Founder and Partner at DesignMap gave a refreshing talk that puts designing products for work into a whole new perspective. He shared with us his journey from studying design at RISD and how he gained appreciation for designing enterprise products.
As technology becomes more widely available and entrenched in peoples’ lives at home, their expectations around ease of use and design aesthetics continue to rise for products they use at work. Long gone are the ’90s when mostly what we expected from productivity software was automating repetitive manual tasks. Consumer expectations are forcing businesses to give design a seat at the table. Here at DesignMap we are fortunate to have help our clients integrate design into their culture and make kick ass products. Sometimes we are even around to see it pay off like when ExactTarget, a long-term DesignMap client, was acquired by Salesforce for $2.5 billion.
Yes, designing for Enterprise can be sexy because of the monetary opportunity and that designers are well positioned to make the applications look beautiful. We learned from Nathan’s talk that according to the Bureau of Labor Statistics, Americans age 25-54 spend an average of 53% of their waking hours at work. So working on designing enterprise products allow us to to do what we love and at the same time have huge positive impact on people’s lives too!
Nathan called for designers working on enterprise products to contribute to the conversation. So, share your stories with us!
Design at Scale: An ExactTarget Case Study
A review of how Design at Scale happen in our work with ExactTarget, looking specifically at Technology complexity, Project scope, a large User base, Data volume and Design communication. and the patterns and best practices that emerged.
Design, the Importance of Research, and a Call to Arms
Presentation for Allscripts Developer Partner conference -- Jared Spool's story about the $300m button, a baseline understanding of the difference between interaction and visual design, the importance of feed-back and feed-forward research, and some practical tools to get folks started.
Design Thinking Meetup: Sparkle-ize It (or, what to do when you get a napkin)
Every designer has had the experience at one point or another of having someone (usually a Product Manager, sometimes an Engineer) draw a screen for them, and ask them to take it and make it look good. Tools like Balsamiq and Axure are only making this more common. Writers, Product Managers and Engineers -- pretty much everyone with a boss or a coworker has experienced someone coming to them and assuming they were the end of the important process and just needed a little polish.
This happens for one (or many) of several reasons:
- They don't have time to think about or discuss alternatives
- They think it's the best solution
- They don't know how to connect the picture that's in their head with the goals they have in mind (or if they connect).
- They think you have little to offer besides making tarting up their idea ("Make it sparkly")
Too often, Designers assume point #4, get insulted, but sparkle-ize it anyway. It's demoralizing and often results in sub-par products (they are at least not as good as they could be). This happens in other contexts too: Researchers tell Product Managers how they should change their products. Designers tell Engineers how they should implement what's designed. Most of us are guilty of assuming #4 at some point, whatever our roll is.
This talk is about how to "reverse out" design thinking. How to look at a napkin drawing and work with the person who drew it to understand what their goals were when they made it, and to propose alternative solutions.
Conversely, if you think in solutions and can't help handing scribbles on napkins to your colleagues, it's about how to back out your own thought process and get more and better contributions from your colleagues.
Either way, it's about better solutions.
(Related blog post at http://www.designmap.com/practice/sparkle-ize-it/)
More Related Content
Viewers also liked
Practice: Design "Swarms"
A quick talk on things we love: in this case, knitting while on phone calls (to "hack" the urge to multitask in a way that supports better focus), but most of the talk is on a new form of massively multi-designer brainstorming we're calling a "design swarm".
Design at Scale: A Storage Case Study
A case study of designing at scale for an enterprise client in the storage vertical. A review of what we mean by "Consumerization of the Enterprise." Do we mean designing IN or FOR enterprise?
And 4th order design: the enterprise system, managing and designing alongside a complex B2B sales channel, old-fashioned challenges with engineers, and reaching “customers”.
DesignMap (hearts) Slack
Learn why Slack is the medium of choice for ad-hoc synchronous and asynchronous conversation.
Enterprise is Sexy
Nathan Kendrick, Founder and Partner at DesignMap gave a refreshing talk that puts designing products for work into a whole new perspective. He shared with us his journey from studying design at RISD and how he gained appreciation for designing enterprise products.
As technology becomes more widely available and entrenched in peoples’ lives at home, their expectations around ease of use and design aesthetics continue to rise for products they use at work. Long gone are the ’90s when mostly what we expected from productivity software was automating repetitive manual tasks. Consumer expectations are forcing businesses to give design a seat at the table. Here at DesignMap we are fortunate to have help our clients integrate design into their culture and make kick ass products. Sometimes we are even around to see it pay off like when ExactTarget, a long-term DesignMap client, was acquired by Salesforce for $2.5 billion.
Yes, designing for Enterprise can be sexy because of the monetary opportunity and that designers are well positioned to make the applications look beautiful. We learned from Nathan’s talk that according to the Bureau of Labor Statistics, Americans age 25-54 spend an average of 53% of their waking hours at work. So working on designing enterprise products allow us to to do what we love and at the same time have huge positive impact on people’s lives too!
Nathan called for designers working on enterprise products to contribute to the conversation. So, share your stories with us!
Design at Scale: An ExactTarget Case Study
A review of how Design at Scale happen in our work with ExactTarget, looking specifically at Technology complexity, Project scope, a large User base, Data volume and Design communication. and the patterns and best practices that emerged.
Design, the Importance of Research, and a Call to Arms
Presentation for Allscripts Developer Partner conference -- Jared Spool's story about the $300m button, a baseline understanding of the difference between interaction and visual design, the importance of feed-back and feed-forward research, and some practical tools to get folks started.
Design Thinking Meetup: Sparkle-ize It (or, what to do when you get a napkin)
Every designer has had the experience at one point or another of having someone (usually a Product Manager, sometimes an Engineer) draw a screen for them, and ask them to take it and make it look good. Tools like Balsamiq and Axure are only making this more common. Writers, Product Managers and Engineers -- pretty much everyone with a boss or a coworker has experienced someone coming to them and assuming they were the end of the important process and just needed a little polish.
This happens for one (or many) of several reasons:
- They don't have time to think about or discuss alternatives
- They think it's the best solution
- They don't know how to connect the picture that's in their head with the goals they have in mind (or if they connect).
- They think you have little to offer besides making tarting up their idea ("Make it sparkly")
Too often, Designers assume point #4, get insulted, but sparkle-ize it anyway. It's demoralizing and often results in sub-par products (they are at least not as good as they could be). This happens in other contexts too: Researchers tell Product Managers how they should change their products. Designers tell Engineers how they should implement what's designed. Most of us are guilty of assuming #4 at some point, whatever our roll is.
This talk is about how to "reverse out" design thinking. How to look at a napkin drawing and work with the person who drew it to understand what their goals were when they made it, and to propose alternative solutions.
Conversely, if you think in solutions and can't help handing scribbles on napkins to your colleagues, it's about how to back out your own thought process and get more and better contributions from your colleagues.
Either way, it's about better solutions.
(Related blog post at http://www.designmap.com/practice/sparkle-ize-it/)
Viewers also liked (9)
Design, the Importance of Research, and a Call to Arms
Design, the Importance of Research, and a Call to Arms
Design Thinking Meetup: Sparkle-ize It (or, what to do when you get a napkin)
Design Thinking Meetup: Sparkle-ize It (or, what to do when you get a napkin)
Precentacion w
- 1. precentacion