Of course, we could have jumped headfirst into designing the atomic units of this system right way, but without everyone agreeing how these components interacted with one another, we would have got bogged down discussing unnecessary details without a clear vision of where we were heading. How do these elements feed back to one another? How does this system interact with other systems? By continuing to probe, we were left with the following system:Īs you can see, what looks like a straightforward problem at the outset has an incredibly complex system behind it. No sooner have you answered one question then you’re left with another that needs answering. Most of these questions have a domino effect. How do articles get created? How do articles get delivered to people? Next, we mapped out how these elements were connected and their inputs and outputs. It has an author, content, and ways for users to give feedback on the article. So we asked ourselves: What are the core elements in this system? For us it was an “article” – content written by the company to provide answers to common questions. This helps users resolve their questions faster, and lets support teams focus on questions that need deeper investigations. With Articles, we were creating a product to help users answer simple support questions themselves. These questions are the foundations of systems thinking, and armed with this thinking process you can start applying them to the specific problem you’re going to tackle. Interconnections: How are the elements connected? What are the relationships? What are their inputs and outputs?.
“It’s like choosing furniture when you don’t know how big your room is” It’s like choosing furniture when you don’t know how big your room is yet. But designing specific interactions this early can get in the way of designing the foundations of your product. The temptation for many designers is to jump straight into designing the interface. When my town got a new library about 6 years ago, they displayed several architects' models and had the public vote after that, they voted on different bids from contractors.If your product design process looks anything like ours, each project will start with a clear set of problems to solve. This is often true in the case of public buildings.
Sometimes, there is even a bid process with the architect. I wonder if this could be checked out during the initial bid process. I think there could be a problem with building construction contractors who lack solid contacts. This sounds like a great option on paper, except for one thing. Or maybe you could request names and references to be included in the construction bids. You don't want to find out in court that the only areas actually covered are those in the construction section!Īpril 26, - That's a good point, though you could try to avoid this problem by getting personal recommendations. I know someone who overlooked this, and got stung quite badly.
#System designer contract how to#
What do you all think? Does anybody have any good tips or experience on how to work with this kind of contract?Īs with all building contracts, check out the insurance liability with the contractor before accepting a bid. I guess design and build contracts are by their very nature a package deal. So even if you have paid for the drawings and love the design you cannot take them elsewhere. I've also heard that that the designs they made for you are usually under copyright law (check the fine print of their contract). Though part of me thinks that streamlining the building process could be good, I'm just really leery about the fact that you can't shop around after you start the process. I have to say, I don't know how I feel about design and build contracts - I've heard so many mixed things about them.
0 kommentar(er)
