Creating something from nothing is an unpredictable journey. The first mile births a new idea into existence, and the final mile is all about letting go. We love talking about starts and finishes, even though the middle stretch is the most important and often the most ignored and misunderstood.    Broken into three sections with 100+ lessons, this no-nonsense book will help you: • Endure the roller coaster of successes and failures by strengthening your resolve, embracing the long-game, and short-circuiting your reward system to get to the finish line. • Optimize what’s working so you can improve the way you hire, better manage your team, and meet your customers’ needs. • Finish strong and avoid the pitfalls many entrepreneurs make, so you can overcome resistance, exit gracefully, and continue onto your next creative endeavor with ease. With insightful interviews from today’s leading entrepreneurs, artists, writers, and executives, as well as Belsky’s own experience working with companies like Airbnb, Pinterest, Uber, and sweetgreen, The Messy Middle will outfit you to find your way through the hardest parts of any bold project or new venture.

    So much so, in fact, that the 12-month design cycles cited in the last edition have shrunk to 6 or even 3 months today. Which is why, more than ever, you need a smart, practical guide that demonstrates how to plan, budget, organize, and manage your Web redesign - or even you initial design - projects from conceptualization to launch. This volume delivers! In these pages Web designer extraordinaire Kelly Goto and coauthor Emily Cotler have distilled their real-world experience into a sound approach to Web redesign workflow that is as much about business priorities as it is about good design. By focusing on where these priorities intersect, Kelly and Emily get straight to the heart of the matter. Each chapter includes a case study that illustrates a key step in the process, and you'll find a plethora of forms, checklists, and worksheets that help you put knowledge into action.This is an AIGA Design Press book published under Peachpit's New Riders imprint in partnership with AIGA.

    - Quick, easy approach and a wealth of case studies give readers a crash course in the difference between good and bad branding. - Tons of tips and real-world advice plus a new branding dictionary help readers turn brand strategy into brand design and execution.

    This environment of constant change will only accelerate in the future and traditional business leaders are ill equipped to deal with it. Just as we took our cues from MBAs and the military in casting the ideal CEO of the 20th century, we can look to design - in its broadest form - to model our future leader, the DEO. These leaders possess characteristics, behaviors and mindsets that allow them to excel in unpredictable, fast-moving and value-charged conditions. They are catalysts for transformation and agents of change. A hybrid of strategic business executive and creative problem-solver, the DEO is willing to take on anything as an object of design and looks at ALL problems as design challenges. Readers will learn not only why this form of leadership is essential to the success of modern organizations, but also what characteristics are best suited to this role. Through intimate conversations with leading DEOs, we explore the mindsets, communities, processes and practices common to creative business leaders. The book lays out--graphically and through example--how DEOs run their companies and why this approach makes sense now. We help readers identify these skills in themselves and their colleagues, and we guide them in using these skills to build, revive or reinvent the next generation of great companies and organization.

    With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system. Now, 45 years after the initial publication of his book, Brooks has revisited his original ideas and added new thoughts and advice, both for readers already familiar with his work and for readers discovering it for the first time.The added chapters contain (1) a crisp condensation of all the propositions asserted in the original book, including Brooks' central argument in The Mythical Man-Month: that large programming projects suffer management problems different from small ones due to the division of labor; that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; (2) Brooks' view of these propositions a generation later; (3) a reprint of his classic 1986 paper "No Silver Bullet"; and (4) today's thoughts on the 1986 assertion, "There will be no silver bullet within ten years."

    But how can you design a voice interface for your mobile app so that users can talk to it? And not just to facilitate question-and-answer sessions, but also provide an engaging, compelling experience?With this practical guide, you ll learn basic voice user interface (VUI) principles for designing mobile apps that makes speech an important tool for interaction. You ll learn how to choose the right speech recognition engine, use best methods for testing VUI on mobile, and dive into advanced VUI design topics to make your VUI not just functional but great.Ideal for product managers, UX designers, and VUI designers, this book explains basic VUI principles for mobile app design, and shows you how to measure the performance of your VUI app and improve upon it. You ll also learn how to determine whether using voice for your app is a good idea in the first placeVUI design is not just about making things cool it s about making a user s experience more natural, more powerful, and more human."

    Most experienced designers would quantify this "legwork" with the term research. By engaging in competitive intelligence, customer profiling, color and trend forecasting, etc., designers are able to bring something to the table that reflects a commercial value for the client beyond a well-crafted logo or brochure. Although scientific and analytical in nature, research is the basis of all good design work. This book provides a comprehensive manual for designers on what design research is, why it is necessary, how to do research, and how to apply it to design work. As designers embrace research methodologies, they share a common vernacular with their clients, and establish respect as idea people. In an increasingly crowded marketplace, embracing research practices will ensure a continued viable role for designers in business. No other books address this issue for student and professional graphic designers. Books on how to do research are usually aimed at writers, business marketers, and scientists. The ability to execute effective research methods is as important to a career in graphic design as the ability to build a grid or layout a page. Understanding the needs of the client and the client's market are essential components of creating value.

    It shows how similar principles can help students understand what people experience when interacting with computers. The book also describes how the user's enjoyment of a computer system should be the biggest design consideration.

    Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. Patterns of Enterprise Application Architecture is written in direct response to the stiff challenges that face enterprise application developers. The author, noted object-oriented designer Martin Fowler, noticed that despite changes in technology--from Smalltalk to CORBA to Java to .NET--the same basic design ideas can be adapted and applied to solve common problems. With the help of an expert group of contributors, Martin distills over forty recurring solutions into patterns. The result is an indispensable handbook of solutions that are applicable to any enterprise application platform. This book is actually two books in one. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book's lessons. The next section, the bulk of the book, is a detailed reference to the patterns themselves. Each pattern provides usage and implementation information, as well as detailed code examples in Java or C#. The entire book is also richly illustrated with UML diagrams to further explain the concepts. Armed with this book, you will have the knowledge necessary to make important architectural decisions about building an enterprise application and the proven patterns for use when building them. The topics covered include - Dividing an enterprise application into layers - The major approaches to organizing business logic - An in-depth treatment of mapping between objects and relational databases - Using Model-View-Controller to organize a Web presentation - Handling concurrency for data that spans multiple transactions - Designing distributed object interfaces

    The

    Above all, this book will help you achieve the promise of agile and iterative delivery: to ensure that the right stuff gets delivered through productive discussions between delivery team members and business stakeholders.

    This book draws on material Michael created for his renowned Object Mentor seminars, techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control. The topics covered include: Understanding the mechanics of software change, adding features, fixing bugs, improving design, optimizing performance Getting legacy code into a test harness Writing tests that protect you against introducing new problems Techniques that can be used with any language or platform, with examples in Java, C++, C, and C# Accurately identifying where code changes need to be made Coping with legacy systems that aren't object-oriented Handling applications that don't seem to have any structureThis book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

    There are updates throughout the book as well. These take into account important advances in cognitive psychology and the science of design while confirming and extending the book's basic thesis: that a physical symbol system has the necessary and sufficient means for intelligent action. The chapter "Economic Reality" has also been revised to reflect a change in emphasis in Simon's thinking about the respective roles of organizations and markets in economic systems."People sometimes ask me what they should read to find out about artificial intelligence. Herbert Simon's book The Sciences of the Artificial is always on the list I give them. Every page issues a challenge to conventional thinking, and the layman who digests it well will certainly understand what the field of artificial intelligence hopes to accomplish. I recommend it in the same spirit that I recommend Freud to people who ask about psychoanalysis, or Piaget to those who ask about child psychology: If you want to learn about a subject, start by reading its founding fathers." -- George A. Miller

    The tools and recipes in this book will help you uncover and solve hidden (and not-so-hidden) problems with your technology, your methodology, and those difficult "people" issues on your team.Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as "post-mortems") are only helpful at the end of the project--too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today.Now, Derby and Larsen show you the tools, tricks, and tips you need to fix the problems you face on a software development project on an on-going basis. You'll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes, and how to scale these techniques up. You'll learn how to deal with problems, and implement solutions effectively throughout the project--not just at the end.With regular tune-ups, your team will hum like a precise, world-class orchestra.ContentsForwardPrefaceIntroduction1. Helping your team inspect and adapt2. A retrospective custom-fit for your team3. Leading retrospectives4. Activities to set the stage5. Activities to gather data6. Activities to gather insights7. Activities to decide what to do8. Activities to close the retrospective9. Releases and project retrospectives10. Make it soA1. Facilitation suppliesA2. Debriefing activitiesA3. Activities quick reference matrixA4. Resources for learning facilitation skillsA5. Bibliography

    Effective layout is essential to communication and enables the end user not only to be drawn in with an innovative design but to digest information easily. Making and Breaking the Grid is a comprehensive layout design workshop that assumes that in order to effectively break the rules of grid-based design, one must first understand those rules and see them applied in real-world projects.Text reveals top designers' work in process and rationale. Projects with similar characteristics are linked through a simple notational system that encourages exploration and comparison of structure ideas. Also included are historical overviews that summarize the development of layout concepts, both grid-based and non-grid based, in modern design practice.