This repository was archived by the owner on Jun 10, 2021. It is now read-only.
Update approach.md #58
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
general edits
tbaxter-18f
reviewed
Dec 9, 2019
| - Week 7 -- Incorporate partner feedback into the final report, run a project post-mortem | ||
|
|
||
| While this is an 8-week project, you'll likely need to restrict the data collection part of the engagement to two weeks or so. Scheduling participants takes a lot of time. Analyzing interviews takes a lot of time. If you try to do more interviews than you can fit in two weeks, *you'll run out of time and budget very quickly*. Keep in mind that the point of a path analysis is to get a better understanding of the partner's problem. Go broad, not deep. You can (and should!) suggest additional work to delve more deeply into the issues you uncover here. | ||
| Remember, you can start the report/presentation at any time or alter this schedule as needed to fit the shape of your engagement. Most projets will have both a slide deck and a paper, consider the slide deck the movie trailer, and the paper the script. |
There was a problem hiding this comment.
Suggested change
| Remember, you can start the report/presentation at any time or alter this schedule as needed to fit the shape of your engagement. Most projets will have both a slide deck and a paper, consider the slide deck the movie trailer, and the paper the script. | |
| Remember, you can start the report/presentation at any time or alter this schedule as needed to fit the shape of your engagement. Most projects will have both a slide deck and a report — consider the slide deck the movie trailer, and the report the full movie. |
tbaxter-18f
reviewed
Dec 9, 2019
| Remember, you can start the report/presentation at any time or alter this schedule as needed to fit the shape of your engagement. Most projets will have both a slide deck and a paper, consider the slide deck the movie trailer, and the paper the script. | ||
|
|
||
| At the same time, however, there are usually delays in scheduling interviews in the vast majority of projects. So do all you can to encourage your client to help contact potential interviewees as quickly as possible. Then prepare for the case that scheduling still spills over into week 2, for instance, which may push interviews into week 4. | ||
| While this is an 8 week project, you'll likely need to restrict the data collection part of the engagement to two weeks or so. Scheduling participants takes a lot of time. Analyzing interviews takes a lot of time. If you try to do more interviews than you can fit in two weeks, *you'll run out of time and budget very quickly*. Keep in mind that the point of a path analysis is to get a better understanding of the partner's problem. Go broad, not deep. You can (and should!) suggest additional work to delve more deeply into the issues you uncover here. It is not recommended to interview more than 12 folks. |
There was a problem hiding this comment.
Suggested change
| While this is an 8 week project, you'll likely need to restrict the data collection part of the engagement to two weeks or so. Scheduling participants takes a lot of time. Analyzing interviews takes a lot of time. If you try to do more interviews than you can fit in two weeks, *you'll run out of time and budget very quickly*. Keep in mind that the point of a path analysis is to get a better understanding of the partner's problem. Go broad, not deep. You can (and should!) suggest additional work to delve more deeply into the issues you uncover here. It is not recommended to interview more than 12 folks. | |
| While this is an 8 week project, you'll likely need to restrict the data collection part of the engagement to two weeks or so. Scheduling participants and analyzing interviews both take a lot of time. If you try to do more interviews than you can fit in two weeks, *you'll run out of time and budget very quickly*. It is not recommended to interview more than 12 folks. | |
| Keep in mind that the point of a path analysis is to get a better understanding of the partner's problem. Go broad, not deep. You can (and should!) suggest additional work to delve more deeply into the issues you uncover here. |
tbaxter-18f
reviewed
Dec 9, 2019
|
|
||
| - **Meet with the partner regularly** (at least weekly) to discuss what you're working on, share insights, and ask questions. Get clear early on about what meeting tools will work for everyone, and use video calls if possible. | ||
| - **Send a "Weekly Ship:"** a quick report emailed to the client at the end of each week. Here's the [Weekly Ship template](https://docs.google.com/document/d/1ulPzFvBLunXm3MD0xL8nPzlJDOoFJbNLPo0Sl6ph99Q/edit), an example of a [Weekly Ship doc](https://docs.google.com/document/d/1uWNqM_2I3i1-UAysYxXt9C3UN_892sJoeeUV0z6wPhM/edit#heading=h.lg378il4ug92), and [the Weekly Ship origin story](https://docs.google.com/document/d/1tdbh_rmIsRgMEBQXh5x6fVAAE4ajUHj8eZ2eFF4acO0/edit#). We also share Weekly Ships in #the-shipping-news Slack channel, so we can see what's happening across projects. | ||
| - **Meet with the partner regularly** (at least weekly) to discuss what you're working on, share insights, and ask questions. Get clear early on about what meeting tools will work for everyone, and use video calls if possible. Include partners in stand-ups. |
There was a problem hiding this comment.
Include partners in stand-ups is such a good tip, it makes me want to spool up another section on modelling agile practices and human-centered design. No change needed, just thinking out loud.
tbaxter-18f
reviewed
Dec 9, 2019
| You can start writing your final report/presentation on day one of your path analysis, if you choose. This can mean outlining, starting a scratch document for recommendations, or sending preliminary findings in each weekly ship. | ||
|
|
||
| The [PA report template](https://docs.google.com/document/d/1DBgwnnHuvR2fAojOwjP8gZ3_jA9pEAGRRKOnmH69d0s/edit) offers lots of structure and advice to work with, even before you begin the drafing process. | ||
| The [PA report template](https://docs.google.com/document/d/1DBgwnnHuvR2fAojOwjP8gZ3_jA9pEAGRRKOnmH69d0s/edit) offers lots of structure and advice to work with, even before you begin the drafing process. You can restructure this report as you see fit to be tailored to what the partner needs. For example, if your partner wants next steps up front, you can move actionable items to the beginning of the paper. |
There was a problem hiding this comment.
Suggested change
| The [PA report template](https://docs.google.com/document/d/1DBgwnnHuvR2fAojOwjP8gZ3_jA9pEAGRRKOnmH69d0s/edit) offers lots of structure and advice to work with, even before you begin the drafing process. You can restructure this report as you see fit to be tailored to what the partner needs. For example, if your partner wants next steps up front, you can move actionable items to the beginning of the paper. | |
| The [PA report template](https://docs.google.com/document/d/1DBgwnnHuvR2fAojOwjP8gZ3_jA9pEAGRRKOnmH69d0s/edit) offers lots of structure and advice to work with, even before you begin the drafting process. You can restructure this report as you see fit to be tailored to what the partner needs. For example, if your partner wants next steps up front, you can move actionable items to the beginning of the paper. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
general edits- when teams can start the paper; changed client to partner in spots where we used client; updated outdated information.