For those who are tired of all-nighters, missed deadlines, and playing catch-up, help is at hand.

A young architect's search for new architectural values in a time of economic crisis. I paused at the stoop and thought this could be the basis of a good book. The story of a young man who went deep into the bowels of the academy in order to understand architecture and found it had been on his doorstep all along. This had an air of hokeyness about it, but it had been a tough couple of days and I was feeling sentimental about the warm confines of the studio which had unceremoniously discharged me upon the world.—from Down Detour Road What does it say about the value of architecture that as the world faces economic and ecological crises, unprecedented numbers of architects are out of work? This is the question that confronted architect Eric Cesal as he finished graduate school at the onset of the worst financial meltdown in a generation. Down Detour Road is his journey: one that begins off-course, and ends in a hopeful new vision of architecture. Like many architects of his generation, Cesal confronts a cold reality. Architects may assure each other of their own importance, but society has come to view architecture as a luxury it can do without. For Cesal, this recognition becomes an occasion to rethink architecture and its value from the very core. He argues that the times demand a new architecture, an empowered architecture that is useful and relevant. New architectural values emerge as our cultural values shift: from high risks to safe bets, from strong portfolios to strong communities, and from clean lines to clean energy.This is not a book about how to run a firm or a profession; it doesn't predict the future of architectural form or aesthetics. It is a personal story—and in many ways a generational one: a story that follows its author on a winding detour across the country, around the profession, and into a new architectural reality.

Offers state-of-the-art principles and strategies gleaned from high-profile projects to help readers manage design This guide to managing design process within the commercial design and construction industry addresses a growing pain point in an industry where collaborative approaches to project delivery are outpacing the way professionals work. It synthesizes issues by investigating the “why,” “how,” and “who” of the discipline of managing design, and gives the “what” and “when” to apply the solutions given various project delivery and contracting methods. The book features candid interviews with over 40 industry leaders—architects, engineers, contractors, owners, educators, technology evangelists, and authors—which present a broad look at current issues and offer paths to future collaboration and change. Managing Design: Conversations, Project Controls and Best Practices for Commercial Design and Construction Projects is a self-help book for design and construction that provides aninsider’s look at the mysteries of managing design for yourself, team, firm and future. It tackles client empathy; firm culture; owner leadership; design and budgets; dealing with engineers, consultants, and contractors; contracts; team assembly; and much more. Features eye-opening interviews with 40 industry luminaries Exposes issues and poses solutions to longstanding industry ills Offers a project design controls framework and toolset for immediate application and action Includes best practice tips, process diagrams, and comparative analytical tables to support the text Written in a relatable style, Managing Design: Conversations, Project Controls and Best Practices for Commercial Design and Construction Projects is a welcome resource for owners, contractors, and designers in search of better ways to work together. “Managing Design blends practical advice from the author's five decades in architecture and construction with wisdom from more than three dozen luminaries in the design, delivery, ownership and operation of the built environment. The result is an extraordinary guide to integrating practice across disciplines.” —Bob Fisher, Editor-In-Chief, Design Intelligence “Managing Design peers into the soul of a contentious industry as it grapples with change—a deep dive into the design and construction process in the words of those doing the work. I enjoyed the engineers and contractors’ pleas to be made parties to design process early on. The questions—as interesting as the answers—are both here in this book.” —Richard Korman, Deputy Editor, Engineering News Record “Managing Design hits many of the design and construction industry’s ills head-on with insightful interviews by new and established leaders and real-world tactics on creating better teams, better communications between players, and—most vitally—better project results.” —Rebecca W. E. Edmunds, AIA, Editor, Author and President, r4 llc

As the digital economy changes the rules of the game for enterprises, the role of software and IT architects is also transforming. Rather than focus on technical decisions alone, architects and senior technologists need to combine organizational and technical knowledge to effect change in their company’s structure and processes. To accomplish that, they need to connect the IT engine room to the penthouse, where the business strategy is defined. In this guide, author Gregor Hohpe shares real-world advice and hard-learned lessons from actual IT transformations. His anecdotes help architects, senior developers, and other IT professionals prepare for a more complex but rewarding role in the enterprise. This book is ideal for: Software architects and senior developers looking to shape the company’s technology direction or assist in an organizational transformation Enterprise architects and senior technologists searching for practical advice on how to navigate technical and organizational topics CTOs and senior technical architects who are devising an IT strategy that impacts the way the organization works IT managers who want to learn what’s worked and what hasn’t in large-scale transformation

Part narrative, part business book; Architect + Entrepreneur is filled with contemporary, relevant, fresh tips and advice, from a seasoned professional architect building a new business. The guide advocates novel strategies and tools that merge entrepreneurship with the practice of architecture and interior design. The Problem:Embarking on a new business venture is intimidating; you have questions. But many of the resources available to help entrepreneur architects and interior designers start their design business lack timeliness and relevance. Most are geared toward building colossal firms like SOM and Gensler using outdated methods and old business models. If you're an individual or small team contemplating starting a design business, this is your field guide; crafted to inspire action. The Solution:Using the lean startup methodology to create a minimum viable product, the handbook encourages successive small wins that support a broader vision enabling one to, "think big, start small, and learn fast." It's a unique take on design practice viewed through the lens of entrepreneurship and is designed to answer the questions all new business owners face, from the rote to the existential. Questions about: - Startup costs - Business models (old and new) - Marriage of business and design - Mindset - Branding & naming (exercises and ideas) - Internet marketing strategies - Passive income ideas - Setting your fee - Taxes - Standard Operating Procedures (SOPs) - Securing the work - Client relations - Software - Billing rates - Contracts Building a business isn't a singular act; it's a series of small steps. Using the outline found in Architect + Entrepreneur you can start today. The chapters are organized to guide you from idea to action. Rather than write a business plan you'll be challenged to craft a brand and you'll sell it using new technologies. Follow the guide sequentially and you'll have both the tools and a profitable small business.

This is your essential one stop shop for information on starting and running a practice. Case studies and advice from practitioners, big and small, run alongside outlines of all the key topics, to give you an insight into the problems and challenges others have faced when setting up a design business. Accessible and informative, this handbook is the ideal first point of reference when starting a practice. Architects have many different reasons for setting up in practice; equally, there are many ways of running your own business. This handbook helps you consider whether or not you should set up on your own, examining issues such as financing, office space, recruitment, IT and workingo ut a business plan. Some architects want to stay small, while others have ambitions to grow into large businesses. Some grow big accidentally. And then there are those who pick and choose their work carefully, and even turn down undesirable contracts, while others will grab at everything possible. This book woudl explore these different models and illustrate how different kinds of practice develop into successful businesses. Importantly, the book will stress that these issues are crucial - you may be the best designer in the world, but unless your business is well managed you will fail. On the other hand, some successful architects spend a lot of time looking for new work and attending to management issues, rarely finding the time for design work. This book would illustrate how architects have struck a balance between these two extremes.

This is a practical guide for software developers, and different than other software architecture books. Here's why: It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face. It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties. It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts. It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail. It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.