Blog Protocol - Use the blog for updates you want to share with the extended internal TSGN team.
- Blog every time you have information to share. Err on the side of blogging too much - you're not flooding anyone's email box, unless they've chosen to subscribe, in which case they want the email notification.
- Repeat after me: "Informal sharing can be easy. Informal sharing can be easy. Informal sharing can be easy..."
- Be concise. Put yourself in your reader's shoes - if I saw this at a glance, would I want to read it.
- Write for scan-ability. A good blog post titles helps, and so does a good first line (that will appear in the blog feed on the wiki homepage).
- Actively invite feedback, and try to be specific on what would be most helpful to you.
- Be mindful that this is not a highly secure site. Don't fail the "headline test."
Projects Protocol [STILL BEING DEVELOPED] - A Project page on this wiki is intended to be a quick overview.
- Required categories are:
- Key Links and Tools
- Problem Definition
- Goals and Outputs
- Critical Indicators/Metrics
- High-Level Timeline
- Roles and Responsibilities
- Funding
Engagement (of Partners) Protocol for TSG Employees [STILL BEING DEVELOPED]
PROTOTYPE: Working With TSGN Partners |