[I4trust] Syncing DIHs Journey

[Angeles Tejado]

Hi Juanjo

The deliverable 2.1 is not finished as nobody commented nor completed the
pending sections and therefore I am waiting for the onboarding to be
finished D1.5 DIH Onboarding Kit
<https://docs.google.com/document/d/1nGEnlMB8Vjs6bsnGdDUsTYRWlp-JjY6gKqHo9TSABKg/edit?usp=sharing>
so
do not use it as a reference. Precisely the community building part is work
in progress and related to the whole action plan (timming and action for
communications).

The complete customer journey is in the communication plan as this is a
pure MarCom funnel. Will be a part of the community strategy chapter
together with the community entry points. That means DIHs
onboarding:community management and comms related, Ambassadors: community
management, comms and marketing related; scouting: SMEs activation and
comms related; etc...

Regarding your question: "shouldn't we also explain to DIHs how we expect
they will support in the journey of SMEs?

Target audiences and channels are defined in the comms plan. DIHs are a
"channel" to reach SMEs and this will be perfectly defined in the comms
plan. How DIHs will support the journey from your tech perspective is
*scouting*, from our side is a comms kit for Ambassadors to attract SMEs
including all the info that an SME needs to know if they want to share data
or if they have data, info on the verticals, kind of experiments... It is a
landing page with the logos and challenges

It is comms. But as I said, waiting for you to finish the onboarding to
align. When I shared the D.2.1 I was expecting to work in those pending
sections together but I see that those sections will be part of the
Onboarding Kit so I can take from there and adapt.

Best



On Wed, 14 Apr 2021 at 01:38, Juanjo Hierro <juanjose.hierro at fiware.org>
wrote:

> Dear Rajiv,
>
>   You have added a chapter focused on the DIH Journey within the D1.5 DIH
> Onboarding Kit
> <https://docs.google.com/document/d/1nGEnlMB8Vjs6bsnGdDUsTYRWlp-JjY6gKqHo9TSABKg/edit?usp=sharing>
> .
>
>   Steps, with their corresponding description, should align with
> steps/phases in section 3.1.6 Methodology
> <https://docs.google.com/document/d/1o-4nnGn6zjNFJH9txLA7YCXyg-10mNCvZX9H3N6KfoA/edit#heading=h.sq6zffnxhykk>
> of deliverable D2.1 - Communication and Dissemination Plan M6
> <https://docs.google.com/document/d/1o-4nnGn6zjNFJH9txLA7YCXyg-10mNCvZX9H3N6KfoA/edit?usp=sharing>.
> On the other hand, I believe that there are contents you generated that are
> nice.
>
>   Could you propose a new version of the Journey considering the phases in
> section 3.1.6 of D2.1 that Angeles can peer review ?
>
>   This way everything gets aligned when we tell DIHs what are the journeys
> we expect they will go through.
>
>   Question: shouldn't we also explain to DIHs how we expect they will
> support in the journey of SMEs?  I tend to believe so and therefore we
> should describe that somewhere in D1.5.  Again, it follows the steps/phases
> described in 3.1.6, but we may focus on where within that journey we expect
> that DIHs will contribute and how.
>
>   An editorial comment: rather that explaining the DIH journey as a
> chapter right after the introduction in D1.5, I would go for creating a
> section within the chapter "The role of Digital Innovation Hubs (DIHs"
> titled "DIH Journey" right after the section describing i4Trust
> Ambassadors.  Rationale is that I believe that within description of the
> Journey we need to talk about LEBDS, Ambassadors, etc, therefore it is
> better if the definition has been given before.
>
>   Cheers,
> --
> Juanjo Hierro
> Chief Technology Officer
> juanjose.hierro at fiware.org
> www.linkedin.com/in/jhierro
> Twitter: @fiware <https://twitter.com/fiware> @JuanjoHierro
> <https://twitter.com/JuanjoHierro>
>
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/i4trust/attachments/20210414/6a2ac6d9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: foundation-logo.png
Type: image/png
Size: 8201 bytes
Desc: not available
URL: <https://lists.fiware.org/private/i4trust/attachments/20210414/6a2ac6d9/attachment.png>