Now, after a unique, five-year study of more than 5,000 managers and employees, Morten Hansen reveals the answers in his “Seven Work Smarter Practices” that can be applied by anyone looking to maximize their time and performance.Each of Hansen’s seven practices is highlighted by inspiring stories from individuals in his comprehensive study. You’ll meet a high school principal who engineered a dramatic turnaround of his failing high school; a rural Indian farmer determined to establish a better way of life for women in his village; and a sushi chef, whose simple preparation has led to his restaurant (tucked away under a Tokyo subway station underpass) being awarded the maximum of three Michelin stars. Hansen also explains how the way Alfred Hitchcock filmed Psycho and the 1911 race to become the first explorer to reach the South Pole both illustrate the use of his seven practices (even before they were identified).Each chapter contains questions and key insights to allow you to assess your own performance and figure out your work strengths, as well as your weaknesses. Once you understand your individual style, there are mini-quizzes, questionnaires, and clear tips to assist you focus on a strategy to become a more productive worker. Extensive, accessible, and friendly, Great at Work will help you achieve more by working less, backed by unprecedented statistical analysis.

    Just about everyone thinks they know how they got there. Just about everyone is wrong. For all that's been written about the Four over the last two decades, no one has captured their power and staggering success as insightfully as Scott Galloway.Instead of buying the myths these compa-nies broadcast, Galloway asks fundamental questions. How did the Four infiltrate our lives so completely that they're almost impossible to avoid (or boycott)? Why does the stock market forgive them for sins that would destroy other firms? And as they race to become the world's first trillion-dollar company, can anyone chal-lenge them?In the same irreverent style that has made him one of the world's most celebrated business professors, Galloway deconstructs the strategies of the Four that lurk beneath their shiny veneers. He shows how they manipulate the fundamental emotional needs that have driven us since our ancestors lived in caves, at a speed and scope others can't match. And he reveals how you can apply the lessons of their ascent to your own business or career.Whether you want to compete with them, do business with them, or simply live in the world they dominate, you need to understand the Four.

    An essential book that unlocks the secrets of highly successful groups and provides readers with a toolkit for building a cohesive, innovative culture, from the New York Times bestselling author of The Talent Code

    In fact, generating accurate estimates is straightforward—once you understand the art of creating them.In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation—distilling academic information and real-world experience into a practical guide for working software professionals. Instead of arcane treatises and rigid modeling techniques, this guide highlights a proven set of procedures, understandable formulas, and heuristics that individuals and development teams can apply to their projects to help achieve estimation proficiency.

    Dr. Sutton reveals new insights that he's learned since the writing of Good Boss, Bad Boss. Sutton adds revelatory thoughts about such legendary bosses as Ed Catmull, Steve Jobs, A.G. Lafley, and many more, and how you can implement their techniques. If you are a boss who wants to do great work, what can you do about it? Good Boss, Bad Boss is devoted to answering that question. Stanford Professor Robert Sutton weaves together the best psychological and management research with compelling stories and cases to reveal the mindset and moves of the best (and worst) bosses. This book was inspired by the deluge of emails, research, phone calls, and conversations that Dr. Sutton experienced after publishing his blockbuster bestseller The No Asshole Rule. He realized that most of these stories and studies swirled around a central figure in every workplace: THE BOSS. These heart-breaking, inspiring, and sometimes funny stories taught Sutton that most bosses - and their followers - wanted a lot more than just a jerk-free workplace. They aspired to become (or work for) an all-around great boss, somebody with the skill and grit to inspire superior work, commitment, and dignity among their charges. As Dr. Sutton digs into the nitty-gritty of what the best (and worst) bosses do, a theme runs throughout Good Boss, Bad Boss - which brings together the diverse lessons and is a hallmark of great bosses: They work doggedly to "stay in tune" with how their followers (and superiors, peers, and customers too) react to what they say and do. The best bosses are acutely aware that their success depends on having the self-awareness to control their moods and moves, to accurately interpret their impact on others, and to make adjustments on the fly that continuously spark effort, dignity, and pride among their people.

    In a brilliant and unconventional book, Phil Rosenzweig unmasks the delusions that are commonly found in the corporate world. These delusions affect the business press and academic research, as well as many bestselling books that promise to reveal the secrets of success or the path to greatness. Such books claim to be based on rigorous thinking, but operate mainly at the level of storytelling. They provide comfort and inspiration, but deceive managers about the true nature of business success.The most pervasive delusion is the Halo Effect. When a company's sales and profits are up, people often conclude that it has a brilliant strategy, a visionary leader, capable employees, and a superb corporate culture. When performance falters, they conclude that the strategy was wrong, the leader became arrogant, the people were complacent, and the culture was stagnant. In fact, little may have changed -- company performance creates a Halo that shapes the way we perceive strategy, leadership, people, culture, and more.Drawing on examples from leading companies including Cisco Systems, IBM, Nokia, and ABB, Rosenzweig shows how the Halo Effect is widespread, undermining the usefulness of business bestsellers from "In Search of Excellence" to "Built to Last" and "Good to Great."Rosenzweig identifies nine popular business delusions. Among them:"The Delusion of Absolute Performance: " Company performance is relative to competition, not absolute, which is why following a formula can never guarantee results. Success comes from doing things better than rivals, which means that managers have to take risks."The Delusion of Rigorous Research: " Many bestselling authors praise themselves for the vast amount of data they have gathered, but forget that if the data aren't valid, it doesn't matter how much was gathered or how sophisticated the research methods appear to be. They trick the reader by substituting sizzle for substance."The Delusion of Single Explanations: " Many studies show that a particular factor, such as corporate culture or social responsibility or customer focus, leads to improved performance. But since many of these factors are highly correlated, the effect of each one is usually less than suggested.In what promises to be a landmark book, "The Halo Effect" replaces mistaken thinking with a sharper understanding of what drives business success and failure. "The Halo Effect" is a guide for the thinking manager, a way to detect errors in business research and to reach a clearer understanding of what drives business success and failure.Skeptical, brilliant, iconoclastic, and mercifully free of business jargon, Rosenzweig's book is nevertheless dead serious, making his arguments about important issues in an unsparing and direct way that will appeal to a broad business audience. For managers who want to separate fact from fiction in the world of business, "The Halo Effect" is essential reading -- witty, often funny, and sharply argued, it's an antidote to so much of the conventional thinking that clutters business bookshelves.

    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.

    "His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique. "The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers--it is a future classic." --Ralph Johnson, author of Design Patterns "If you don't think you are getting value from your investment in object-oriented programming, this book will tell you what you've forgotten to do. "Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion." --Dave Collins, author of Designing Object-Oriented User Interfaces "Eric weaves real-world experience modeling--and building--business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric's descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field." --Luke Hohmann, author of Beyond Software Architecture "This book belongs on the shelf of every thoughtful software developer." --Kent Beck "What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important." --Kyle Brown, author of Enterprise Java(TM) Programming with IBM(R) WebSphere(R) The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process. Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development. Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis--refactoring not just the code but the model underlying the code--in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:Getting all team members to speak the same language Connecting model and implementation more deeply Sharpening key distinctions in a model Managing the lifecycle of a domain object Writing domain code that is safe to combine in elaborate ways Making complex code obvious and predictable Formulating a domain vision statement Distilling the core of a complex domain Digging out implicit concepts needed in the model Applying analysis patterns Relating design patterns to the model Maintaining model integrity in a large system Dealing with coexisting models on the same project Organizing systems with large-scale structures Recognizing and responding to modeling breakthroughs With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.

    So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems?In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient--lessons directly applicable to your organization.This book is divided into four sections: Introduction--Learn what site reliability engineering is and why it differs from conventional IT industry practicesPrinciples--Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE)Practices--Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systemsManagement--Explore Google's best practices for training, communication, and meetings that your organization can use

    People need to be effective.Productivity books focus on doing more, Jim and Tonianne want you to focus on doing better. Personal Kanban is about choosing the right work at the right time. Recognizing why we do the things we do. Understanding the impact of our actions. Creating value - not just product. For ourselves, our families, our friends, our co-workers. For our legacy.Personal Kanban takes the same Lean principles from manufacturing that led the Japanese auto industry to become a global leader in quality, and applies them to individual and team work. Personal Kanban asks only that we visualize our work and limit our work-in-progress. Visualizing work allows us to transform our conceptual and threatening workload into an actionable, context-sensitive flow. Limiting our work-in-progress helps us complete what we start and understand the value of our choices. Combined, these two simple acts encourage us to improve the way we work and the way we make choices to balance our personal, professional, and social lives.Neither a prescription nor a plan, Personal Kanban provides a light, actionable, achievable framework for understanding our work and its context. This book describes why students, parents, business leaders, major corporations, and world governments all see immediate results with Personal Kanban.

    Team leads usually have little to no idea how to handle people related issues – issues that affect how the morale, quality of work, and overall performance of the team, and of course impacts how easy or hard it is to implement “the new stuff”.Most team leaders are clueless as to how to handle their manager giving them an impossible due date, a team member reluctant to try anything new, or another team member teaching all the other members practices from 25 years ago that today only hurt the team.Why?No one teaches that to software team leads. Team leads today, in the overwhelming majority of places, are just developers who worked hard and stayed with the company long enough to be promoted. But they have no people or management skills - and those are very painfully needed when you are trying to drive the things you believe in inside an organization that has very little interest in changing.Team leadership is the next big thing that software developers need to conquer, or none of this unit testing, TDD, Agile or Lean thing is going to catch on, except in very small circles, that, by chance, happen to have the right people leading their teams.

    Showing how salesforce.com not only survived the dotcom implosion of 2001, but went on to define itself as the leader of the cloud computing revolution and spark a $46-billion dollar industry, Benioff's story will help business leaders and entrepreneurs stand out, innovate better, and grow faster in any economic climate. In Behind the Cloud, Benioff shares the strategies that have inspired employees, turned customers into evangelists, leveraged an ecosystem of partners, and allowed innovation to flourish.

    It’s not about to-do lists and accountability charts. It’s about creating a framework for regular check-ins, key results, and most of all, the beauty of a good fail – and how to take a temporary disaster and turn it into a future success. In this book, Wodtke takes you through the fictional case study of Hanna and Jack, who are struggling to survive in their own startup. They fight shiny object syndrome, losing focus, and dealing with communication issues. After hard lessons, they learn the practical steps they need to do what must be done. The second half of the book demonstrates how to use Objectives and Key Results (OKRs) to help teams realize big goals in a methodical way, leaving nothing to chance. Laid out in a practical but compelling way, she makes the lessons of Hanna and Jack’s story clear and actionable. Ready to move your team in the right direction? Read this, and learn the system of creating your focus – and finding success. "Busy grinding without purpose is the secret death of too many startups. In this memorable story, Christina gives us a glimpse of a more satisfying kind of startup--still hard and chaotic but full of purpose and the chance to build something great." James Cham, Founder, Bloomberg Beta "This book is useful, actionable, and actually fun to read! If you want to get your team aligned around real, measurable goals, Radical Focus will teach you how to do it quickly and clearly." -Laura Klein, Principal, Users Know "Someone once told me that 'problems are just opportunities that haven’t presented themselves'. Since I was introduced to OKRs, they've been an invaluable tool for me, and our company. Christina's ideas have been instrumental, allowing me to better navigate the often ambiguous approach to goal setting and along the way creating a more open and accountable team and a clearer path for myself professionally. I personally can't thank her enough for the guidance." Scott Baldwin, Director of Services, Yellow Pencil "Radical Focus illustrates how to implement OKRs in an engaging, compact, realistic story. Best of all, Wodtke proves OKRs can be fun!" Ben Lamorte, OKRs.com

    In addition, the completely updated fifth edition shows you how to build trust and confidence, be an active listener, manage a diverse group of individuals, conduct performance appraisals, and address many other challenges that come with the manager's job.Written in an inviting and accessible style, this classic skill-building book is an essential tool for becoming an effective, confident new manager."

    This book demystifies agile methodologies: why they’re designed the way they are, what problems they address, and the values, principles, and ideas they embody.Learning Agile helps you recognize the principles that apply to development problems specific to your team, company, and projects. You’ll discover how to use that information to guide your choice of methodologies and practices.With this book you’ll learn:Values that effective software teams possessThe methodologies that embody those valuesThe practices that make up those methodologiesAnd principles that help you bring those values, methodologies, and practices to your team and your company