�ݺ�ߣ

Editor's Notes

• #6: Audience participation. A lot of designers think they are working on enterprise software, but aren’t really. There’s some kind of collaboration aspect to it.
• #9: Supply chain management. Enough said. Most designers avoid enterprise because it’s really hard and they can’t relate to it. Tell “Explaining Apptio to your parents” story.
• #10: This is the server farm I have in my place. I have a $100 million IT budget, so I use Apptio. John from IT.
• #11: Most enterprise companies have very tough engineering cultures, and they don’t necessarily want to bring designers along for the ride. You have to learn how to sell to them, and this is going to be a lot of painful conversations.
• #12: Super political organizations. Most people in enterprise have been in it for a very long time, and are good at working the system.
• #14: Columbus, no product roadmap, pivoted without his knowledge, didn’t even know he was addressing a different set of personas. Apptio, a product that takes at least 90 days to light up. Guess A/B testing isn’t work. escrow.com, 21 day transactions. Credit: https://ercerp.wordpress.com/how-long-does-it-take-to-implement-erp/
• #15: We are our own worst enemy. Have to stay at a place long enough to learn the domain so we can be effective, and if you think you’ve accomplished something by being at a company for a year, you’re fooling yourself. We’re typically the one’s calling others because we believe in measurement.
• #17: Custom built solutions within organizations are going away, looking to applications they can implement and get value from, faster. At Apptio, we call it rip and replace. Companies are finding it easier to use SaaS applications that solve most of their needs and can realize business value quickly than building huge applications that take years to complete.
• #18: Companies are stumbling over themselves to get into it. IBM, SAP, Workday. http://www.gartner.com/newsroom/id/1963815
• #19: Money tree dance.
• #21: The iPhone changed everything. Expecting purpose built applications and better holistic experiences. Willing to make tradeoffs if the experience is easier.
• #23: Applications are opening up. Internet of things, web services, services oriented architecture, mobile, virtual workplaces.
• #24: Steve Yegge article, a must read:https://plus.google.com/+RipRowan/posts/eVeouesvaVX
• #26: It’s gotta be top down, and it has to be a vision that can be put into action. Eight Organizational Challenges for UX Professionals - http://www.usabilitycounts.com/2012/05/02/eight-organizational-challenges-for-ux-professionals/. John Maeda, Design in Tech Report http://www.kpcb.com/blog/design-in-tech-report-2015
• #27: The foundation. Don’t hire an agency. Hire in-house designers. 10 to 1 ratios are bad. 5 to 1 ratios are good. Include a design leader that can recruit and sell the idea because they’re going to have to sell it hard.
• #28: Pabini Gabriel-Petit. Hire design leaders that can come in and build a team, and know what the competencies are.
• #29: Five years to build a design culture at most organizations. It’s a lot of small wins instead of a big win that builds trust.
• #30: The profile of who you hire is almost as important. Mix in researchers that are domain experts with designers that come from a consumer background but have dealt with complex workflows. A lot of places had requirements like, “must hire designers with financial software experience” so they get financial software looking stuff.
• #31: Create a culture where designers can learn, fail and grow. Pair them with Subject Matter Experts to learn about the system. Pair them with developers to work collaboratively, which means designers have to be in-house. It’s going to take about a year before you know if they really get it. Set your expectations appropriately.
• #32: Customers are not the users. For enterprise, success is usually considered the sale. Tell Apptio story. Add analytics to the right things. Help. The application. Establish the right metrics, which means iterations. Establish goals.
• #33: This is a culture thing. Change the selling motion by avoiding feature-based selling. Sell the experience and business value, don’t sell to RFP. Teach people about jobs and outcomes, not going straight to the solution without understanding the problem.
• #34: Five years to build a design culture at most organizations. It’s a lot of small wins instead of a big win that builds trust.
• #35: Five years to build a design culture at most organizations. It’s a lot of small wins instead of a big win that builds trust.
• #36: There’s a lot of opportunity in Enterprise, considering the wicked problems we face. Tell content strategy story for Apptio and Carl Chatfield. Tell the story about Jon Fox.
• #38: You’re going to be in a position of weakness and feeling stupid for a long time. Be humble and listen to everyone. Be flexible. Admit lack of knowledge.
• #39: Say you don’t know anything.
• #40: Make a two to three year commitment at a company and become a domain expert. You can’t do good enterprise design working as a consultant. Lost in Translation moments. Marry the problem and find something interesting about it. 30 hours story.
• #41: Tell the “have things, get things” story. Enterprise software companies are very protective of their language. It helps to understand the language, but sometimes the users don’t even understand it.
• #42: Data Visualization Guidelines story.
• #43: Data Visualization Guidelines.
• #44: http://www.uie.com/brainsparks/2015/05/20/uietips-designing-without-a-designer/ Designing without a designer. You won’t be able to design everything because you’ll constantly be resource constrained. Turn the developers into designers. Develop a lot of system patterns they can use and teach them how to design. We have a data visualization guidelines document that’s much shorter than reading a Stephen Few book, and much more prescriptive. User researchers can also be used in innovative ways.
• #45: Break out the problems in smaller chunks and even propose smaller applications. Think configurable, not customizable. We do a lot of one day workshops.
• #46: Customer. SmartSheet, Zip Recruiter, Yammer, Trello, Asana, Slack. We call it looking for the rouge analyst that doesn’t want to work with IT. You’ll learn more about the customer at a smarter scale, and the bottom up approach becomes very social.
• #47: Look at smaller flows and look at longer journeys. Develop metrics and outcomes you want achieve. Jobvite, 85 clicks to 45 clicks.