But what if everyone is wrong?In their acclaimed bestseller The Challenger Sale, Matthew Dixon and his colleagues at CEB busted longstanding myths about sales. Now they've turned to a new vital business subject - customer loyalty - with a book that turns conventional wisdom on its head.Companies devote untold time and resources trying to dazzle customers. Yet CEB's careful research proves that is wildly overrated: loyalty has a lot more to do with how well companies deliver on their basic promises than on how dazzling the service experience might be. Forget bells and whistles and just solve your customer's problems. The Effortless Experience lays out the four pillars of a low-effort customer experience, with robust data, in­sights and profiles. Here are tools and templates you can start applying right away to improve service, reduce costs, and ultimately generate the elusive loyalty that the 'dazzle factor' fails to deliver.The rewards are there for the taking, and the pathway to achieving them is now clearly marked.'A business detective story, in which cherished truths are systematically investigated-and frequently debunked' -Dan Heath, coauthor of Decisive, Switch, and Made to StickMatt Dixon is Executive Director of the Sales & Service Practice at CEB. He is a frequent contributor to the Harvard Business Review, and his previous book, The Challenger Sale, was a Wall Street Journal bestsellerNick Toman is Senior Director of Research for CEB's Sales & Services Practice and is a frequent contributor to the Harvard Business Review.Rick DeLisi is Senior Director of Advisory Services for CEB's Sales & Service Practice and a noted public speaker and facilitator.

    Product Mastery explores the traits of the best product owners offering an insight into the difference between good and great product ownership and explaining how the best product owners are DRIVEN to be successful.In a follow up to the hugely successful Scrum Mastery, Geoff Watts shares more enlightening case studies on how to be:Decisive with incomplete information.Ruthless about maximizing value and minimizing risk.Informed about your product’s domain.Versatile in your leadership style.Empowering of project stakeholders.Negotiable while you pursue your vision.This is essential reading for anyone involved in an agile product development effort.Geoff Watts has been a thought leader in the agile development space for many years and his books, training and coaching have helped thousands of teams across the world deliver better products more effectively.Geoff is the author of Scrum Mastery: From Good to Great Servant-Leadership and The Coach’s Casebook: Mastering The Twelve Traits That Trap Us, a winner of the 2016 International Book Awards."Product Mastery is a great book to read if you want to understand how a great Product Owner works. Whether you are hiring a Product Owner or want to be a great Product Owner, the insights that Geoff Watts shares in this book should be your guide."--Jeff Sutherland, Co-Creator of Scrum and author of Scrum: The Art of Doing Twice The Work in Half the Time“Geoff has done a great job at distilling the soft skills product owners need to succeed. His new book is packed with practical advice to advance your skills and become a truly great product owner.”– Roman Pichler, Author of Strategize and Agile Product Management with Scrum.

    We want them to buy something, read more, or take action of some kind. Designing without understanding what makes people act the way they do is like exploring a new city without a map: results will be haphazard, confusing, and inefficient. This book combines real science and research with practical examples to deliver a guide every designer needs. With it you'll be able to design more intuitive and engaging work for print, websites, applications, and products that matches the way people think, work, and play.Learn to increase the effectiveness, conversion rates, and usability of your own design projects by finding the answers to questions such as: What grabs and holds attention on a page or screen?What makes memories stick?What is more important, peripheral or central vision?How can you predict the types of errors that people will make?What is the limit to someone's social circle?How do you motivate people to continue on to (the next step?What line length for text is best?Are some fonts better than others? These are just a few of the questions that the book answers in its deep-dive exploration of what makes people tick.

    Reprint. 25,000 first printing.

    Dr. Robert Cialdini is the seminal expert in the rapidly expanding field of influence and persuasion. His thirty-five years of rigorous, evidence-based research along with a three-year program of study on what moves people to change behavior has resulted in this highly acclaimed book.You'll learn the six universal principles, how to use them to become a skilled persuader—and how to defend yourself against them. Perfect for people in all walks of life, the principles of Influence will move you toward profound personal change and act as a driving force for your success.

    Louis glassblowing artist and recovering computer scientist named Jim McKelvey lost a sale because he couldn't accept American Express cards. Frustrated by the high costs and difficulty of accepting credit card payments, McKelvey joined his friend Jack Dorsey (the cofounder of Twitter) to launch Square, a startup that would enable small merchants to accept credit card payments on their mobile phones. With no expertise or experience in the world of payments, they approached the problem of credit cards with a new perspective, questioning the industry's assumptions, experimenting and innovating their way through early challenges, and achieving widespread adoption from merchants small and large.But just as Square was taking off, Amazon launched a similar product, marketed it aggressively, and undercut Square on price. For most ordinary startups, this would have spelled the end. Instead, less than a year later, Amazon was in retreat and soon discontinued its service. How did Square beat the most dangerous company on the planet? Was it just luck? These questions motivated McKelvey to study what Square had done differently from all the other companies Amazon had killed. He eventually found the key: a strategy he calls the Innovation Stack.McKelvey's fascinating and humorous stories of Square's early days are blended with historical examples of other world-changing companies built on the Innovation Stack to reveal a pattern of ground-breaking, competition-proof entrepreneurship that is rare but repeatable.The Innovation Stack is a thrilling business narrative that's much bigger than the story of Square. It is an irreverent first-person look inside the world of entrepreneurship, and a call to action for all of us to find the entrepreneur within ourselves and identify and fix unsolved problems--one crazy idea at a time.

    This guide also helps you understand the many data-mining techniques in use today.Based on an MBA course Provost has taught at New York University over the past ten years, Data Science for Business provides examples of real-world business problems to illustrate these principles. You’ll not only learn how to improve communication between business stakeholders and data scientists, but also how participate intelligently in your company’s data science projects. You’ll also discover how to think data-analytically, and fully appreciate how data science methods can support business decision-making.Understand how data science fits in your organization—and how you can use it for competitive advantageTreat data as a business asset that requires careful investment if you’re to gain real valueApproach business problems data-analytically, using the data-mining process to gather good data in the most appropriate wayLearn general concepts for actually extracting knowledge from dataApply data science principles when interviewing data science job candidates

    And in a perfect world, those who produce the best code are the most successful. But in our perfectly messy world, success also depends on how you work with people to get your job done.In this highly entertaining book, Brian Fitzpatrick and Ben Collins-Sussman cover basic patterns and anti-patterns for working with other people, teams, and users while trying to develop software. It's valuable information from two respected software engineers whose popular video series, "Working with Poisonous People," has attracted hundreds of thousands of viewers.You'll learn how to deal with imperfect people--those irrational and unpredictable beings--in the course of your work. And you'll discover why playing well with others is at least as important as having great technical skills. By internalizing the techniques in this book, you'll get more software written, be more influential, be happier in your career.

    Great ideas often come from a simple spark: A soccer player on the New Zealand national team notices all the unused wool his country produces and figures out a way to turn them into shoes (Allbirds). A former Buddhist monk decides the very best way to spread his mindfulness teachings is by launching an app (Headspace). A sandwich cart vendor finds a way to reuse leftover pita bread and turns it into a multimillion-dollar business (Stacy’s Pita Chips).   Award-winning journalist and NPR host Guy Raz has interviewed more than 200 highly successful entrepreneurs to uncover amazing true stories like these. In How I Built This, he shares tips for every entrepreneur’s journey: from the early days of formulating your idea, to raising money and recruiting employees, to fending off competitors, to finally paying yourself a real salary. This is a must-read for anyone who has ever dreamed of starting their own business or wondered how trailblazing entrepreneurs made their own dreams a reality.

    Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects. Describes practical, effective, field-tested techniques for managing the requirements engineering process from end to end. Provides examples demonstrating how requirements "good practices" can lead to fewer change requests, higher customer satisfaction, and lower development costs. Fully updated with contemporary examples and many new practices and techniques. Describes how to apply effective requirements practices to agile projects and numerous other special project situations. Targeted to business analysts, developers, project managers, and other software project stakeholders who have a general understanding of the software development process. Shares the insights gleaned from the authors' extensive experience delivering hundreds of software-requirements training courses, presentations, and webinars.New chapters are included on specifying data requirements, writing high-quality functional requirements, and requirements reuse. Considerable depth has been added on business requirements, elicitation techniques, and nonfunctional requirements. In addition, new chapters recommend effective requirements practices for various special project situations, including enhancement and replacement, packaged solutions, outsourced, business process automation, analytics and reporting, and embedded and other real-time systems projects.

    But all too often when we interact with people—especially those who report to us—we simply tell them what we think they need to know. This shuts them down. To generate bold new ideas, to avoid disastrous mistakes, to develop agility and flexibility, we need to practice Humble Inquiry.Ed Schein defines Humble Inquiry as “the fine art of drawing someone out, of asking questions to which you do not know the answer, of building a relationship based on curiosity and interest in the other person.” In this seminal work, Schein contrasts Humble Inquiry with other kinds of inquiry, shows the benefits Humble Inquiry provides in many different settings, and offers advice on overcoming the cultural, organizational, and psychological barriers that keep us from practicing it.

    Find out how the Swedish police combined XP, Scrum, and Kanban in a 60-person project. From start to finish, you'll see how to deliver a successful product using Lean principles. We start with an organization in desperate need of a new way of doing things and finish with a group of sixty, all working in sync to develop a scalable, complex system. You'll walk through the project step by step, from customer engagement, to the daily "cocktail party," version control, bug tracking, and release. In this honest look at what works--and what doesn't--you'll find out how to: Make quality everyone's business, not just the testers. Keep everyone moving in the same direction without micromanagement. Use simple and powerful metrics to aid in planning and process improvement. Balance between low-level feature focus and high-level system focus. You'll be ready to jump into the trenches and streamline your own development process.ContentsForewordPrefacePART I: HOW WE WORK1. About the Project1.1 Timeline 51.2 How We Sliced the Elephant 61.3 How We Involved the Customer 72. Structuring the Teams3. Attending the Daily Cocktail Party3.1 First Tier: Feature Team Daily Stand-up3.2 Second Tier: Sync Meetings per Specialty3.3 Third Tier: Project Sync Meeting4. The Project Board4.1 Our Cadences4.2 How We Handle Urgent Issues and Impediments5. Scaling the Kanban Boards6. Tracking the High-Level Goal7. Defining Ready and Done7.1 Ready for Development7.2 Ready for System Test7.3 How This Improved Collaboration 8. Handling Tech Stories8.1 Example 1: System Test Bottleneck8.2 Example 2: Day Before the Release8.3 Example 3: The 7-Meter Class9. Handling Bugs9.1 Continuous System Test9.2 Fix the Bugs Immediately9.3 Why We Limit the Number of Bugs in the Bug Tracker9.4 Visualizing Bugs9.5 Preventing Recurring Bugs10. Continuously Improving the Process10.1 Team Retrospectives10.2 Process Improvement Workshops10.3 Managing the Rate of Change11. Managing Work in Progress11.1 Using WIP Limits11.2 Why WIP Limits Apply Only to Features12. Capturing and Using Process Metrics12.1 Velocity (Features per Week)12.2 Why We Don’t Use Story Points12.3 Cycle Time (Weeks per Feature)12.4 Cumulative Flow12.5 Process Cycle Efficiency13. Planning the Sprint and Release13.1 Backlog Grooming13.2 Selecting the Top Ten Features13.3 Why We Moved Backlog Grooming Out of the Sprint Planning Meeting13.4 Planning the Release14. How We Do Version Control14.1 No Junk on the Trunk14.2 Team Branches14.3 System Test Branch15. Why We Use Only Physical Kanban Boards16. What We Learned16.1 Know Your Goal16.2 Experiment16.3 Embrace Failure16.4 Solve Real Problems16.5 Have Dedicated Change Agents16.6 Involve PeoplePART II: A CLOSER LOOK AT THE TECHNIQUES 17. Agile and Lean in a Nutshell17.1 Agile in a Nutshell17.2 Lean in a Nutshell17.3 Scrum in a Nutshell17.4 XP in a Nutshell17.5 Kanban in a Nutshell18. Reducing the Test Automation Backlog18.1 What to Do About It18.2 How to Improve Test Coverage a Little Bit Each Iteration18.3 Step 1: List Your Test Cases18.4 Step 2: Classify Each Test18.5 Step 3: Sort the List in Priority Order18.6 Step 4: Automate a Few Tests Each Iteration18.7 Does This Solve the Problem?19. Sizing the Backlog with Planning Poker19.1 Estimating Without Planning Poker19.2 Estimating with Planning Poker19.3 Special Cards20. Cause-Effect Diagrams20.1 Solve Problems, Not Symptoms20.2 The Lean Problem-Solving Approach: A3 Thinking20.3 How to Use Cause-Effect Diagrams20.4 Example 1: Long Release Cycle20.5 Example 2: Defects Released to Production20.6 Example 3: Lack of Pair Programming20.7 Example 4: Lots of Problems20.8 Practical Issues: How to Create and Maintain the Diagrams20.9 Pitfalls20.10 Why Use Cause-Effect Diagrams?21. Final WordsA1. Glossary: How We Avoid Buzzword BingoIndex

    In this book, you'll learn how to become an entrepreneur, driving your career in the direction of your choosing. You'll learn how to build your software development career step by step, following the same path that you would follow if you were building, marketing, and selling a product. After all, your skills themselves are a product. The choices you make about which technologies to focus on and which business domains to master have at least as much impact on your success as your technical knowledge itself--don't let those choices be accidental. We'll walk through all aspects of the decision-making process, so you can ensure that you're investing your time and energy in the right areas. You'll develop a structured plan for keeping your mind engaged and your skills fresh. You'll learn how to assess your skills in terms of where they fit on the value chain, driving you away from commodity skills and toward those that are in high demand. Through a mix of high-level, thought-provoking essays and tactical "Act on It" sections, you will come away with concrete plans you can put into action immediately. You'll also get a chance to read the perspectives of several highly successful members of our industry from a variety of career paths. As with any product or service, if nobody knows what you're selling, nobody will buy. We'll walk through the often-neglected world of marketing, and you'll create a plan to market yourself both inside your company and to the industry in general. Above all, you'll see how you can set the direction of your career, leading to a more fulfilling and remarkable professional life.

    Testing Business Ideas aims to reverse that statistic. In the tradition of Alex Osterwalder's global bestseller Business Model Generation, this practical guide contains a library of hands-on techniques for rapidly testing new business ideas.Testing Business Ideas explains how systematically testing business ideas dramatically reduces the risk and increases the likelihood of success for any new venture or business project. It builds on the internationally popular Business Model Canvas and Value Proposition Canvas by integrating Assumptions Mapping and other powerful lean startup-style experiments.Testing Business Ideas uses an engaging 4-color format to:Increase the success of any venture and decrease the risk of wasting time, money, and resources on bad ideas Close the knowledge gap between strategy and experimentation/validation Identify and test your key business assumptions with the Business Model Canvas and Value Proposition Canvas A definitive field guide to business model testing, this book features practical tips for making major decisions that are not based on intuition and guesses. Testing Business Ideas shows leaders how to encourage an experimentation mindset within their organization and make experimentation a continuous, repeatable process.

    Sutton addressed a taboo topic that affects every workplace: employees who are insensitive to their colleagues, corporate bullies, bosses who just don't get it, the kind of people who make you exclaim in exasperation, "What an asshole!"Now, in a definitive book that addresses this growing problem, Sutton shows you how you can work with unsavory people without becoming one of them yourself.