{"id":4164,"date":"2020-12-25T09:30:12","date_gmt":"2020-12-25T08:30:12","guid":{"rendered":"http:\/\/mariusursu.com\/?post_type=jetpack-portfolio&p=4164"},"modified":"2021-10-07T17:35:38","modified_gmt":"2021-10-07T15:35:38","slug":"appendix-working-with-empathy-iterations","status":"publish","type":"jetpack-portfolio","link":"https:\/\/mariusursu.com\/index.php\/portfolio\/appendix-working-with-empathy-iterations\/","title":{"rendered":"Appendix: Embedding Design in an Organization"},"content":{"rendered":"\n

This article adds more detail to the points which I touched on in the Visual and Short version \ud83d\udd17<\/a>. <\/em> <\/p>\n\n\n\n

This is an Appendix, for reference only and linked from there. <\/em><\/p>\n\n\n\n

<\/div>\n\n\n\n
\n
\n

Table of contents:<\/h2>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

The Client<\/a>
The Design Challenge<\/a><\/p>\n\n\n\n

Research<\/strong><\/a>
wide and qualitative<\/a>
~~ Persona: user is not equal to customer<\/a>
~~ the enterprise blockchain landscape<\/a><\/p>\n<\/div>\n\n\n\n

\n

Orchestration<\/a><\/strong>
(individual) Interactions < (meaningful) User Journeys<\/a>
~~ Moodboards & Design System<\/a>
~~ Rapid click-through prototypes<\/a>
~~ exploring the creation of a Marketplace<\/a><\/p>\n\n\n\n

Organizational change<\/strong><\/a>
making space for Design<\/a>
~~ a new Process for implementating<\/a>
~~ positive signs of change<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n

<\/div>\n\n\n\n
<\/div>\n\n\n\n

The Client<\/h2>\n\n\n\n
\n
\n

A strong and highly technical team with experience in blockchain integration projects<\/strong><\/p>\n<\/div>\n\n\n\n

\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n
<\/div>\n\n\n\n
\n
\n

Unchain.io is a validated and funded small company, at the time of writing consisting of 10 people. The goal of the company is to bridge business applications with various types of enterprise blockchain networks.<\/p>\n\n\n\n

The starting point for this freelance project was a high fidelity prototype<\/strong> built as a technical demo. The prototype had not been sufficiently validated<\/strong> with relevant parties, even though there were plans to build even more functionality.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\n
\n
<\/span> More background on the team:<\/div>
<\/p>\n\n\n\n


The team had been doing personalized consultancy and implementation work in enterprise blockchain for years. By working across organizations and industries<\/strong>, they had identified some common challenges<\/strong> and a value proposition to support their partners by automating certain integration tasks<\/strong>.<\/p>\n\n\n\n


While Unchain.io had strong technical skills in-house<\/strong>, the design expertise<\/strong> was not built within the team and was outsourced to freelancers<\/strong>.<\/p>\n\n\n\n


In addition, the predominant attitude was to show the product for feedback only “when it is ready”, not a moment earlier.<\/strong> This could be due to wanting to defend one’s own work from criticism<\/strong> and to not damage one’s reputation<\/strong>.<\/p>\n\n\n\n

<\/div><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

<\/div>\n\n\n\n

The Design Challenge<\/h2>\n\n\n\n
\n
\n

The freelance project was scoped around the usefulness and usability<\/strong> of the digital platform. It must serve the users (beginners as well as experts) in achieving objectives set forward by their organizations. <\/p>\n\n\n\n

Secondary goal: investigating the creation of a marketplace<\/strong> for modular software integrations. This would involve encouraging the re-use of software created by other organizations.<\/p>\n<\/div>\n<\/div>\n\n\n\n

<\/div>\n\n\n\n

Appendix 1. Research – wide and qualitative<\/h2>\n\n\n\n
<\/div>\n\n\n\n

This is an Appendix, I recommend seeing the Visual and Short version \ud83d\udd17<\/a>.<\/em><\/strong><\/em><\/p>\n\n\n\n

<\/div>\n\n\n\n
<\/div>\n\n\n\n
\n
\n

In Service Design<\/strong>, there are more unknowns and more stakeholders to take into account compared to UI\/UX Design<\/strong>, where the problem space is more defined. Empathy <\/strong>and an in depth knowledge of the personas is<\/strong> not enough<\/strong>. It is important to have the same in-depth understanding of all relevant stakeholders,<\/strong> both in isolation, as well as how they interact<\/strong> between each other.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n