Deliberate Words
by Conspectus, Inc. - decision managers, word masters, aggregators. There is tremendous power in a word that is perfectly placed at the best location, at the best time, during the design and construction process of a project. Deliberate words can manage success, build trust, and provide transparency that every member of the project team craves. As decision managers of the team, Conspectus explores the notion of how transparency transforms three main components of every project: behavior, content, and outcomes, through the appropriate usage of words. Behavior of every participant, is the foundation communication and collaboration, through deliberate words. It will transform the team, and build strong relationships. Content, the documentation built on these relationships, containing deliberate words, is then transformed. The outcome is a successful project, with a legacy of ultimate collaboration. Join us as we chat with members of the architectural, engineering, construction, and owner communities to learn how deliberate word shape their contributions, their projects, and their world! Through these conversations, words aggregate decisions, and transforms perspectives on transparency in the decision-making process.
Deliberate Words
What A Week! Efficiency Without Assumption
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
This week on What a Week, Dave Stutzman, Steve Gantner, and Elias Saltz explore how specification teams can create efficiencies when working on multiple projects for the same architect or owner. When projects share standards, assemblies, and delivery methods, there is an opportunity to build from common information rather than starting from scratch each time.
But efficiency comes with a warning: reused information can easily be mistaken for finished information. When a specification already looks complete, project-specific differences may receive less scrutiny, allowing outdated or incorrect requirements to slip through and potentially lead to conflicts or RFIs.
The conversation looks beyond simply copying projects and considers a more intentional approach: developing common requirements once, then using tools such as tagging to manage the differences between individual projects. Done well, that shared source can support multiple projects and potentially evolve into an owner guide specification. But it still requires ongoing review and maintenance as codes, materials, products, and project needs change.
The takeaway: efficiency comes from building on what you know, not assuming what worked before will work again.