Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tersify summary #74

Merged
merged 1 commit into from Oct 9, 2018
Merged

Tersify summary #74

merged 1 commit into from Oct 9, 2018

Conversation

yatil
Copy link
Contributor

@yatil yatil commented Oct 8, 2018

I think the summary is to much describing what a business case is and benefits from cutting to the chase.

I debated if the four areas of benefits should be linked, but then that would be even more redundant with the Page Contents block, so I didn’t do that.

I think the summary is to much describing what a business case is and benefits from cutting to the chase.

I debated if the four areas of benefits should be linked, but then that would be even more redundant with the Page Contents block, so I didn’t do that.

Signed-off-by: Eric Eggert <mail@yatil.net>
@shawna-slh
Copy link
Contributor

+1 for limiting the summary describing what a business case is. (I proposed this previously. :-)

@vmmiller
Copy link

vmmiller commented Oct 9, 2018

+1 to limit the summary on the business case. (I also made a related comment some time ago.) Rationale as above: I think the summary plus the first heading on essentially "what is a business case+why" takes away from the main interest of this very useful resource.

@sharronrush sharronrush merged commit fd3941e into master Oct 9, 2018
@sharronrush sharronrush deleted the yatil-summary branch October 9, 2018 21:04
@sharronrush
Copy link
Contributor

It was editor's discretion and I am strongly opposed to removing this description because I think there are many who do not understand that a business case need not just say "you will make this much more money for this level of investment" but can also talk about cultural improvements and risk avoidance. Two people outside of EO who read this told me they had not thought previously about how risk analysis - the risk of inaction - was an important argument within the Biz case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants