Thought Leadership voice

The process: 

The review: 

What Liam would need: 

Here are some of my thoughts/suggestions! 

1) Immediately after choosing a Thought Leader (TL), we should set a process in place where we could collectively amass a “dossier” or “file” with the TL’s Twitter feed, past articles, and any other written references to help inform the voice that’s used in the Gitcoin piece. That way we could create mini “style guides” based off the information culled. It’s great for posterity sake, too, because if we ever have repeat TLs there’ll already be a referential point : )

2) I believe it’s already established practice to share the piece with the TL (we did that with Kyle, yes?); but I’d like to extend that further from just a simple “sign-off” and ask that the TL be candid and give solid feedback if necessary on the piece if they believe the voice has strayed from something they themselves would normally put out. At the same time, we probably want to tow a fine line with the TL using this opportunity to “edit” or ask for too many things to be “edited”; in other words, we should be very clear/consistent with our language when we posit this to TLs.

3) On a tactical / logistical level, I’d suggest the following order of operations to work as such (if we act on the above ideas…)a) Thought Leader chosen
b) Create “Dossier/File” 
c) Write TL piece informed Dossier/File
d) All marginal comments are internally resolved
e) One Initial Pass from TL to determine if voice “fits”
f) Editor takes a pass
g) One final read from Gitcoin + final sign off from TL

4) Additionally, unless there’s any major stylistic intricacies/idiosyncrasies that need to be reflected in the TL piece, we should obviously stick to Gitcoin’s general style guide.a) On that note, overall, style guides should be seen as living and modular documents that are constantly being tinkered and amended (my most immediate thought is of the great MMM content call today, where we were discussing veering away from a more explicit web3-based language into something more inclusive, yeah?). 
 

Anyways, those are my initial thoughts and I’m really looking forward to hearing from Laura and Rohit on this as well : )

Table

Gitcoin Thought Leader Profiles

Name

DAO Profile

Twitter Handle

Topics

Kyle Weiss

http//:twitter.com/kbw

Thought Leadership voice

The process: 

The review: 

What Liam would need: 

Here are some of my thoughts/suggestions! 

1) Immediately after choosing a Thought Leader (TL), we should set a process in place where we could collectively amass a “dossier” or “file” with the TL’s Twitter feed, past articles, and any other written references to help inform the voice that’s used in the Gitcoin piece. That way we could create mini “style guides” based off the information culled. It’s great for posterity sake, too, because if we ever have repeat TLs there’ll already be a referential point : )

2) I believe it’s already established practice to share the piece with the TL (we did that with Kyle, yes?); but I’d like to extend that further from just a simple “sign-off” and ask that the TL be candid and give solid feedback if necessary on the piece if they believe the voice has strayed from something they themselves would normally put out. At the same time, we probably want to tow a fine line with the TL using this opportunity to “edit” or ask for too many things to be “edited”; in other words, we should be very clear/consistent with our language when we posit this to TLs.

3) On a tactical / logistical level, I’d suggest the following order of operations to work as such (if we act on the above ideas…)a) Thought Leader chosen
b) Create “Dossier/File” 
c) Write TL piece informed Dossier/File
d) All marginal comments are internally resolved
e) One Initial Pass from TL to determine if voice “fits”
f) Editor takes a pass
g) One final read from Gitcoin + final sign off from TL

4) Additionally, unless there’s any major stylistic intricacies/idiosyncrasies that need to be reflected in the TL piece, we should obviously stick to Gitcoin’s general style guide.a) On that note, overall, style guides should be seen as living and modular documents that are constantly being tinkered and amended (my most immediate thought is of the great MMM content call today, where we were discussing veering away from a more explicit web3-based language into something more inclusive, yeah?). 
 

Anyways, those are my initial thoughts and I’m really looking forward to hearing from Laura and Rohit on this as well : )

Table

Gitcoin Thought Leader Profiles

Name

DAO Profile

Twitter Handle

Topics

Kyle Weiss

http//:twitter.com/kbw