{"id":124547,"date":"2022-05-24T10:12:14","modified":"2024-04-17T16:35:02","slug":"how-expectations-influence-iot-projects","status":"publish","type":"post","link":"https:\/\/legacy.tele-haase.at\/en\/news\/how-expectations-influence-iot-projects\/","title":{"rendered":"How expectations influence IoT projects"},"content":{"rendered":" \n

\n <\/svg> Textblock <\/span>\n <\/h2>\n\n <\/div>\n ","protected":false},"excerpt":{"rendered":"","protected":false},"author":48,"featured_media":124542,"sticky":false,"template":"","format":"standard","categories":[7487,177],"tags":[7476,7279],"acf":{"news_max_hohe":"70vh","news_image":{"ID":124542,"id":124542,"title":"Digital transformation concept. System engineering. Binary code. Programming.","filename":"TELE-IoT-Erwartungsmanagement-scaled.jpg","filesize":145771,"url":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-scaled.jpg","link":"https:\/\/legacy.tele-haase.at\/en\/news\/how-expectations-influence-iot-projects\/attachment\/digital-transformation-concept-system-engineering-binary-code-programming-2\/","alt":"IoT Erwartungsmanagement","author":"48","description":"IoT Erwartungsmanagement","caption":"Digital transformation concept. System engineering. Binary code. Programming.","name":"digital-transformation-concept-system-engineering-binary-code-programming-2","status":"inherit","uploaded_to":124547,"date":"2022-05-24 08:11:16","modified":"2022-05-24 08:17:20","menu_order":0,"mime_type":"image\/jpeg","type":"image","subtype":"jpeg","icon":"https:\/\/legacy.tele-haase.at\/wp-includes\/images\/media\/default.png","width":2048,"height":1150,"sizes":{"thumbnail":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-220x220.jpg","thumbnail-width":220,"thumbnail-height":220,"medium":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-544x360.jpg","medium-width":544,"medium-height":360,"medium_large":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-768x431.jpg","medium_large-width":768,"medium_large-height":431,"large":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-780x520.jpg","large-width":780,"large-height":520,"1536x1536":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-1536x862.jpg","1536x1536-width":1536,"1536x1536-height":862,"2048x2048":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-2048x1150.jpg","2048x2048-width":2048,"2048x2048-height":1150,"hd":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-1920x1078.jpg","hd-width":1920,"hd-height":1078,"galerie":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-320x180.jpg","galerie-width":320,"galerie-height":180,"stellen":"https:\/\/legacy.tele-haase.at\/wp-content\/uploads\/2022\/05\/TELE-IoT-Erwartungsmanagement-400x400.jpg","stellen-width":400,"stellen-height":400}},"news_title":"How expectations influence IoT projects","seo":[{"googleAuthor":"","googlePublisher":"","schemaName":"","schemaDescription":"","schemaImage":false}],"webblocks":[{"acf_fc_layout":"textblock","acf_fc_id":"acf-block-6a14c4ff06d65","acf_fc_style":"","flexible":false,"text":"

Expectation management for the project success<\/h2>\n

IoT projects often fail not because of technical or organizational problems at all, but because of differing expectations among those involved. If the (often hidden) expectations have been neglected, none of the participants is really satisfied with the result. That’s why it’s important to make expectations visible in advance and also to compare them again and again during the project \u2013 expectation management is the key.<\/p>\n

IoT projects are usually implemented very quickly, and agile methods are used during development. This results in a “proof of concept” as quickly as possible, i.e., a minimal version of the future product that is subjected to a practical test at the customer’s site. Since the customer is heavily involved in this approach, his expectations carry a lot of weight here. And this can very easily backfire.<\/p>\n

 <\/p>\n

Product versus prototype<\/h3>\n

First, the proof of concept prototype must be discussed and tested with the customer. So the customer has to invest time and other resources, but at this point often only sees a quickly implemented working sample with minimal functionality.
On the other hand, a proof of concept can also fail. This is not a problem for the development team. It is even good to clearly see the differences between the product idea and the real situation and to go from here into a further development loop. The customer involved, however, is usually not used to such approaches, sees his expectations disappointed and perceives the “back to the start” as a defeat. So even if the field test at the customer site was successful for the project team, the customer may not be satisfied – his expectation was not met. This can lead to disagreements in the customer relationship and the project team has to deal with now missing trust in addition to the technical challenges.<\/p>\n

 <\/p>\n

Know expectations!<\/h3>\n

For this reason, it is incredibly important to clarify mutual expectations in advance. It is not necessarily a matter of having to fulfill all mutual expectations. Rather, the project team should work with the customer to express, write down, sort, prioritize, and delete unrealistic requirements. Those who don’t do this risk reckless and unnecessary disappointment.
By the way, this also applies to internal projects. Management, your own project team or other affected company departments always have expectations. Knowing and evaluating them makes many easier.<\/p>\n

 <\/p>\n

Helpful tips and tricks for practice<\/h3>\n

Expectation management requires a lot of communication and regular meetings. Especially at the beginning of a project, there is an endless need for coordination. The following steps have proven effective in a moderated kick-off:<\/p>\n

 <\/p>\n