The findings will surprise many readers and, quite frankly, upset others.The ChallengeBuilt to Last, the defining management study of the nineties, showed how great companies triumph over time and how long-term sustained performance can be engineered into the DNA of an enterprise from the very beginning. But what about the company that is not born with great DNA? How can good companies, mediocre companies, even bad companies achieve enduring greatness? The StudyFor years, this question preyed on the mind of Jim Collins. Are there companies that defy gravity and convert long-term mediocrity or worse into long-term superiority? And if so, what are the universal distinguishing characteristics that cause a company to go from good to great?The StandardsUsing tough benchmarks, Collins and his research team identified a set of elite companies that made the leap to great results and sustained those results for at least fifteen years. How great? After the leap, the good-to-great companies generated cumulative stock returns that beat the general stock market by an average of seven times in fifteen years, better than twice the results delivered by a composite index of the world's greatest companies, including Coca-Cola, Intel, General Electric, and Merck. The ComparisonsThe research team contrasted the good-to-great companies with a carefully selected set of comparison companies that failed to make the leap from good to great. What was different? Why did one set of companies become truly great performers while the other set remained only good? The FindingsThe findings of the Good to Great study will surprise many readers and shed light on virtually every area of management strategy and practice. The findings include:Level 5 Leaders: The research team was shocked to discover the type of leadership required to achieve greatness.The Hedgehog Concept (Simplicity within the Three Circles): To go from good to great requires transcending the curse of competence.A Culture of Discipline: When you combine a culture of discipline with an ethic of entrepreneurship, you get the magical alchemy of great results. Technology Accelerators: Good-to-great companies think differently about the role of technology.The Flywheel and the Doom Loop: Those who launch radical change programs and wrenching restructurings will almost certainly fail to make the leap.

    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.

    The reality is that most innovations come from a process of rigorous examination through which great ideas are identified and developed before being realized as new offerings and capabilities.This book introduces the idea of design thinking‚ the collaborative process by which the designer′s sensibilities and methods are employed to match people′s needs not only with what is technically feasible and a viable business strategy. In short‚ design thinking converts need into demand. It′s a human−centered approach to problem solving that helps people and organizations become more innovative and more creative.Design thinking is not just applicable to so−called creative industries or people who work in the design field. It′s a methodology that has been used by organizations such as Kaiser Permanente to icnrease the quality of patient care by re−examining the ways that their nurses manage shift change‚ or Kraft to rethink supply chain management. This is not a book by designers for designers; this is a book for creative leaders seeking to infuse design thinking into every level of an organization‚ product‚ or service to drive new alternatives for business and society.

    Drucker reminds us, is the ability to "get the right things done." This usually involves doing what other people have overlooked as well as avoiding what is unproductive. Intelligence, imagination, and knowledge may all be wasted in an executive job without the acquired habits of mind that mold them into results.Drucker identifies five practices essential to business effectiveness that can, and must, be learned: Managing time Choosing what to contribute to the organization Knowing where and how to mobilize strength for best effect Setting the right priorities Knitting all of them together with effective decision-makingRanging widely through the annals of business and government, Peter F. Drucker demonstrates the distinctive skill of the executive and offers fresh insights into old and seemingly obvious business situations.

    Deep inside, we sense that more is possible. We long for soulful workplaces, for authenticity, community, passion, and purpose.In this groundbreaking book, the author shows that every time, in the past, when humanity has shifted to a new stage of consciousness, it has achieved extraordinary breakthroughs in collaboration. A new shift in consciousness is currently underway. Could it help us invent a more soulful and purposeful way to run our businesses and nonprofits, schools and hospitals?A few pioneers have already cracked the code and they show us, in practical detail, how it can be done. Leaders, founders, coaches, and consultants will find this work a joyful handbook, full of insights, examples, and inspiring stories.ADVANCE PRAISE"Congratulations on a spectacular treatise! This is truly pioneering work. In terms of integral sophistication, there is simply nothing like it out there."--Ken Wilber, from the Foreword"The most exciting book I've read in years on organization design and leadership models."--Jenny Wade, Ph.D., Author of Changes of Mind"A book like Reinventing Organizations only comes along once in a decade. Sweeping and brilliant in scope, it is the Good To Great for a more enlightened age. What it reveals about the organizational model of the future is exhilarating and deeply hopeful."--Norman Wolfe, Author of The Living Organization"A comprehensive, highly practical account of the emergent worldview in business. Everything you need to know about building a new paradigm organization!"--Richard Barrett, Chairman and Founder, Barrett Values Center"Frederic Laloux has done business people and professionals everywhere a signal service. He has discovered a better future for organizations by describing, in useful detail, the unusual best practices of today."--Bill Torbert, Author of Action Inquiry"As the rate of change escalates exponentially, the old ways of organizing and educating, which were designed for efficiency and repetition, are dying. Frederic Laloux is one of the few management leaders exploring what comes next. It's deeply different."--Bill Drayton, Founder, Ashoka: Innovators for the Public

    Richard Rumelt shows that there has been a growing and unfortunate tendency to equate Mom-and-apple-pie values, fluffy packages of buzzwords, motivational slogans, and financial goals with “strategy.” He debunks these elements of “bad strategy” and awakens an understanding of the power of a “good strategy.” A good strategy is a specific and coherent response to—and approach for overcoming—the obstacles to progress. A good strategy works by harnessing and applying power where it will have the greatest effect in challenges as varied as putting a man on the moon, fighting a war, launching a new product, responding to changing market dynamics, starting a charter school, or setting up a government program. Rumelt’snine sources of power—ranging from using leverage to effectively focusing on growth—are eye-opening yet pragmatic tools that can be put to work on Monday morning.Surprisingly, a good strategy is often unexpected because most organizations don’t have one. Instead, they have “visions,” mistake financial goals for strategy,and pursue a “dog’s dinner” of conflicting policies and actions.Rumelt argues that the heart of a good strategy is insight—into the true nature of the situation, into the hidden power in a situation, and into an appropriate response. He shows you how insight can be cultivated with a wide variety of tools for guiding yourown thinking.Good Strategy/Bad Strategy uses fascinating examples from business, nonprofit, and military affairs to bring its original and pragmatic ideas to life. The detailed examples range from Apple to General Motors, from the two Iraq wars to Afghanistan, from a small local market to Wal-Mart, from Nvidia to Silicon Graphics, from the Getty Trust to the Los Angeles Unified School District, from Cisco Systems to Paccar, and from Global Crossing to the 2007–08 financial crisis.Reflecting an astonishing grasp and integration of economics, finance, technology, history, and the brilliance and foibles of the human character, Good Strategy/Bad Strategy stems from Rumelt’s decades of digging beyond the superficial to address hard questions with honesty and integrity.From the Hardcover edition.

    The result is a tremendous amount of time and money wasted due to wrong assumptions, lack of focus, poor communication of objectives, lack of understanding and misalignment with overall goals. There has to be a better way to deliver!This handbook is a practical guide to impact mapping, a simple yet incredibly effective method for collaborative strategic planning that helps organisations make an impact with software. Impact mapping helps to create better plans and roadmaps that ensure alignment of business and delivery, and are easily adaptable to change. Impact mapping fits nicely into several current trends in software product management and release planning, including goal-oriented requirements engineering, frequent iterative delivery, agile and lean software methods, lean startup product development cycles, and design thinking.Who is this book for?The primary audience of this book are senior people involved in building software products or delivering software projects, from both business and delivery sides. This includes business sponsors and those whose responsibilities include product ownership, project oversight or portfolio management, architecture, business analysis, quality improvement and assurance and delivery. - Business people assigned to software projects will learn how to communicate their ideas better.- Senior product or project sponsors will learn how to communicate their assumptions more effectively to delivery teams, how to engage delivery teams to make better strategic decisions, and how to manage their project portfolio more effectively.- Delivery teams that are already working under the umbrella of agile or lean delivery methods, and more recently lean startup ideas, will learn how to better focus deliverables and engage business sponsors and users.- Delivery teams moving to agile or lean delivery methods will get ideas on how to address some common issues with scaling these practices, such as creating a big picture view, splitting work into small chunks that still have business value and reporting progress more meaningfully.About the authorGojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko won the 2012 Jolt Award for the best book, was voted by peers as the most influential agile testing professional in 2011, and his blog won the UK Agile Award for the best online publication in 2010. To get in touch, write to gojko@neuri.co.uk or visit http://gojko.net.

    These people are celebrities now. What was it like when they were just a couple friends with an idea? Founders like Steve Wozniak (Apple), Caterina Fake (Flickr), Mitch Kapor (Lotus), Max Levchin (PayPal), and Sabeer Bhatia (Hotmail) tell you in their own words about their surprising and often very funny discoveries as they learned how to build a company.Where did they get the ideas that made them rich? How did they convince investors to back them? What went wrong, and how did they recover?Nearly all technical people have thought of one day starting or working for a startup. For them, this book is the closest you can come to being a fly on the wall at a successful startup, to learn how it's done.But ultimately these interviews are required reading for anyone who wants to understand business, because startups are business reduced to its essence. The reason their founders become rich is that startups do what businesses do--create value--more intensively than almost any other part of the economy. How? What are the secrets that make successful startups so insanely productive? Read this book, and let the founders themselves tell you.

    Previously undocumented, these 23 patterns allow designers to create more flexible, elegant, and ultimately reusable designs without having to rediscover the design solutions themselves.The authors begin by describing what patterns are and how they can help you design object-oriented software. They then go on to systematically name, explain, evaluate, and catalog recurring designs in object-oriented systems. With Design Patterns as your guide, you will learn how these important patterns fit into the software development process, and how you can leverage them to solve your own design problems most efficiently. Each pattern describes the circumstances in which it is applicable, when it can be applied in view of other design constraints, and the consequences and trade-offs of using the pattern within a larger design. All patterns are compiled from real systems and are based on real-world examples. Each pattern also includes code that demonstrates how it may be implemented in object-oriented programming languages like C++ or Smalltalk.

    Christensen says outstanding companies can do everything right and still lose their market leadership -- or worse, disappear completely. And he not only proves what he says, he tells others how to avoid a similar fate.Focusing on "disruptive technology" -- the Honda Super Cub, Intel's 8088 processor, or the hydraulic excavator, for example -- Christensen shows why most companies miss "the next great wave." Whether in electronics or retailing, a successful company with established products will get pushed aside unless managers know when to abandon traditional business practices. Using the lessons of successes and failures from leading companies, "The Innovator's Dilemma" presents a set of rules for capitalizing on the phenomenon of disruptive innovation.

    It was their natural ability to start with why that enabled them to inspire those around them and to achieve remarkable things.In studying the leaders who've had the greatest influence in the world, Simon Sinek discovered that they all think, act, and communicate in the exact same way—and it's the complete opposite of what everyone else does. Sinek calls this powerful idea The Golden Circle, and it provides a framework upon which organizations can be built, movements can be lead, and people can be inspired. And it all starts with WHY.Any organization can explain what it does; some can explain how they do it; but very few can clearly articulate why. WHY is not money or profit—those are always results. WHY does your organization exist? WHY does it do the things it does? WHY do customers really buy from one company or another? WHY are people loyal to some leaders, but not others?Starting with WHY works in big business and small business, in the nonprofit world and in politics. Those who start with WHY never manipulate, they inspire. And the people who follow them don't do so because they have to; they follow because they want to.Drawing on a wide range of real-life stories, Sinek weaves together a clear vision of what it truly takes to lead and inspire. This book is for anyone who wants to inspire others or who wants to find someone to inspire them.

    The Web is awash in Ruby code that is now virtually impossible to change or extend. This text helps you solve that problem by using powerful real-world object-oriented design techniques, which it thoroughly explains using simple and practical Ruby examples. Sandi Metz has distilled a lifetime of conversations and presentations about object-oriented design into a set of Ruby-focused practices for crafting manageable, extensible, and pleasing code. She shows you how to build new applications that can survive success and repair existing applications that have become impossible to change. Each technique is illustrated with extended examples, all downloadable from the companion Web site, poodr.info. The first title to focus squarely on object-oriented Ruby application design, Practical Object-Oriented Design in Ruby will guide you to superior outcomes, whatever your previous Ruby experience. Novice Ruby programmers will find specific rules to live by; intermediate Ruby programmers will find valuable principles they can flexibly interpret and apply; and advanced Ruby programmers will find a common language they can use to lead development and guide their colleagues. This guide will help you Understand how object-oriented programming can help you craft Ruby code that is easier to maintain and upgrade Decide what belongs in a single Ruby class Avoid entangling objects that should be kept separate Define flexible interfaces among objects Reduce programming overhead costs with duck typing Successfully apply inheritance Build objects via composition Design cost-effective tests Solve common problems associated with poorly designed Ruby code

    By presenting actual experiences and analyzing them as they are described, the author conveys the developmental thought processes employed and shows a style of thinking that leads to successful results is something that can be learned. Along with spectacular successes, the author also conveys how failures contributed to shaping the thought processes. Provides the reader with a style of thinking that will enhance a person's ability to function as a problem-solver of complex technical issues. Consists of a collection of stories about the author's participation in significant discoveries, relating how those discoveries came about and, most importantly, provides analysis about the thought processes and reasoning that took place as the author and his associates progressed through engineering problems.

    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

    He needed a way to keep track of software development over time – whatever he was thinking about or working on. He researched subjects he found interesting, then documented his research with a public blog post, which he could easily find and refer to later. Over time, increasing numbers of blog visitors found the posts helpful, relevant and interesting. Now, approximately 100,000 readers visit the blog per day and nearly as many comment and interact on the site.Effective Programming: More Than Writing Code is your one-stop shop for all things programming. Jeff writes with humor and understanding, allowing for both seasoned programmers and newbies to appreciate the depth of his research. From such posts as“The Programmer’s Bill of Rights” and “Why Cant Programmers... Program?” to “Working With the Chaos Monkey,” this book introduces the importance of writing responsible code, the logistics involved, and how people should view it more as a lifestyle than a career.