[I4trust] Syncing DIHs Journey

Juanjo Hierro juanjose.hierro at fiware.org
Wed Apr 14 08:01:31 CEST 2021


Hi,

   What I have proposed and continue proposing is to align in terms of 
steps that Rajiv was proposing with the steps in 3.6.1 of D2.1 which are 
based on a well proven methodology based on your experience.  I believe 
making that alignment would not be that difficult reading contents of 
what Rajiv wrote and you wrote and that alignment would be beneficial 
(among other things when we present both deliverables to reviewers, for 
example).   Section 3.6.1 is focused on communication therefore there 
are elements on what he wrote in D1.5 which may extend, further develop, 
contents of section 3.6.1 and are meaningful to keep in D1.5 because 
that is the deliverable that should contain everything we want DIHs to 
read.  It should be self-contained in that respect.  In the meeting 
about D1.5 we commented that this would mean copying certain parts of 
other deliverables in D1.5 (and that is behind the assignment of people 
to sections of that deliverable) but that is fine because we don't 
pretend to make all deliverables public nor make DIHs reall all the 
deliverables.

   During the peer review of that section in D1.5, besides checking that 
the alignment is appropriate you may decide what may be worth adding in 
section 3.6.1 of D2.1.

   If we find difficulties in the alignment, let's arrange a call.

   Regarding the journey of SMEs, they are one of our target as you well 
explain in D2.1.  My question was more whether we should add some 
explicit section and words about "SMEs journey" in D1.5 which is the kin 
we want DIHs to read.   The scouting performed by the DIHs, is connected 
to activities the DIHs would carried out in connection to this SME 
journey and we agreed we would add a section to describe the scouting 
within D1.5, the same way we agreed to describe multi-tier support in 
D1.5 (high-level because details will go in D1.11) and other pparts.   
Those are elements that explain what we want DIHs to do to jointly 
support with us the SMEs journey.  My point is more whether explicitly 
elaborating on the concept of "SME journey" somewhere in D1.5 makes 
sense and create a connection between support that DIHs should bring in 
that "SME journey" with different sections of the document.  I believe 
it would make sense.   But if everyone believes that is not needed 
because it will be implicit when DIHs read the whole onboarding kit, 
that is also fine with me.

   Cheers,

   Juanjo


On 14/4/21 07:19, Angeles Tejado wrote:
> 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 <mailto: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 <mailto:juanjose.hierro at fiware.org>
>     www.linkedin.com/in/jhierro <https://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/ca756bdf/attachment-0001.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/ca756bdf/attachment-0001.png>


More information about the I4trust mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy