50 change management and git by aassuied-ps · Pull Request #74 · phuse-org/git-in-statistical-programming

aassuied-ps · 2026-06-03T16:00:39Z

Draft PR. Currently, it's just an introduction and titles for topics I think we could work on.

Add an introduction and a plan.

talk about tools

kieranjmartin · 2026-06-26T13:42:27Z

@aassuied-ps I added some content in the suggestions, thanks for starting this!

frostwix

Only reviewed first two sections so far

frostwix · 2026-07-01T01:20:45Z

+
+The Change Curve is a well known model for understanding how employees resond to change @HOLDSWORTH2024254. While there are many different implementations of it, generally speaking it is understood to be split into two main phases, first of resistance and then of acceptance. An important attitude in any company trying to make any sort of change, be it organisational or technological, is to have empathy for those individuals who are experiencing it, and give them the support they need.
+
+We must understand that any change will take time to embed into an organisation, and the main thing we can influence is how fast that change goes, and how well we can adopt the technology.


"and how well we can adopt the technology"--what does this mean?

I have reworded this, see what you think!

Looks good, thanks!

Co-authored-by: frostwix <154441859+frostwix@users.noreply.github.com>

frostwix · 2026-07-17T14:28:08Z

+
+## The Change Curve
+
+The Change Curve is a well known model for understanding how employees respond to change @HOLDSWORTH2024254. While it has many different forms, it generally begins with initial shock, followed by resistance, low morale, gradual experimentation, and then acceptance and integration. An important consideration for any company trying to make any significant change, be it organisational or technological, is to have empathy for those individuals who are experiencing it and give them the support they need.


I imagine we don't want this "@"

Suggested change

The Change Curve is a well known model for understanding how employees respond to change @HOLDSWORTH2024254. While it has many different forms, it generally begins with initial shock, followed by resistance, low morale, gradual experimentation, and then acceptance and integration. An important consideration for any company trying to make any significant change, be it organisational or technological, is to have empathy for those individuals who are experiencing it and give them the support they need.

The Change Curve is a well known model for understanding how employees respond to change. While it has many different forms, it generally begins with initial shock, followed by resistance, low morale, gradual experimentation, and then acceptance and integration. An important consideration for any company trying to make any significant change, be it organisational or technological, is to have empathy for those individuals who are experiencing it and give them the support they need.

frostwix

Minor suggestions

frostwix · 2026-07-17T14:31:17Z

+
+Depending on your company's size and how they want to use Git, there a number of tools to interact with Git and Github. These are covered more in the [appendix](tools.qmd), but your decision is likely to be motivated based on how close you want users to interact with Git.
+
+You may decide that you wish to abstract users access to Git or you might decide that you wish to get users comfortable with direct Git terminal access. Different tools will enable different approaches.


Is this in line with the intention of this sentence?

Suggested change

You may decide that you wish to abstract users access to Git or you might decide that you wish to get users comfortable with direct Git terminal access. Different tools will enable different approaches.

You may choose to hide Git's complexity from users by giving them easy-to-use tools, or you may choose to teach users to work directly with Git commands in the terminal. The tools you select will influence which approach is possible.

frostwix · 2026-07-17T14:32:33Z

+
+There are a number of excellent resources for learning Git online. This means that when creating internal documentation on Git it is important to focus on how your organisation will be using Git in practice.
+
+Your documentation should focus first on the ways someone will work in their day to day, covering the typical flow and where possible integrating it into the tools they are likely to use. Documentation should be easy to access and use, and easy to search. We recommend where possible to not include this level of documentation in GxP training, as the latter is likely to be in systems that can be harder to update quickly based on user feedback.


Suggested change

Your documentation should focus first on the ways someone will work in their day to day, covering the typical flow and where possible integrating it into the tools they are likely to use. Documentation should be easy to access and use, and easy to search. We recommend where possible to not include this level of documentation in GxP training, as the latter is likely to be in systems that can be harder to update quickly based on user feedback.

Your documentation should focus first on the ways someone will work in their day-to-day, covering the typical flow and where possible integrating it into the tools they are likely to use. Documentation should be easy to access and use, and easy to search. We recommend where possible to not include this level of documentation in GxP training, as the latter is likely to be in systems that can be harder to update quickly based on user feedback.

frostwix · 2026-07-17T14:33:07Z

+
+Your documentation should focus first on the ways someone will work in their day to day, covering the typical flow and where possible integrating it into the tools they are likely to use. Documentation should be easy to access and use, and easy to search. We recommend where possible to not include this level of documentation in GxP training, as the latter is likely to be in systems that can be harder to update quickly based on user feedback.
+
+GxP training is of course important to meet our compliance requirements, but we can normally build training on top of it which enables more dyanmic updates as you get feedback from users on what works and what does not. 


Suggested change

GxP training is of course important to meet our compliance requirements, but we can normally build training on top of it which enables more dyanmic updates as you get feedback from users on what works and what does not.

GxP training is of course important to meet our compliance requirements, but we can normally build training on top of it which enables more dynamic updates as you get feedback from users on what works and what does not.

frostwix · 2026-07-17T14:33:37Z

+
+### Failure cases
+
+An important resource to build over time is how to resolve issues that might occur when using Git. The exact nature of the issues are likely to run into will be specific to your organisations workflow but some likely common issues are


Suggested change

An important resource to build over time is how to resolve issues that might occur when using Git. The exact nature of the issues are likely to run into will be specific to your organisations workflow but some likely common issues are

An important resource to build over time is how to resolve issues that might occur when using Git. The exact nature of the issues users are likely to run into will be specific to your organisation's workflow but some likely common issues are

frostwix · 2026-07-17T14:36:20Z

+
+Where possible trainings should be live, and in person if it is possible to arrange, to allow maximum engagement.
+
+One vital aspect is that training should be targetted only at individuals who are going to be adopting the Git workflow very soon, or who are already adopting it. This means that what they have learnt can be applied straight away, removing the danger of knowledge atrophying during use. Related to this, if you can train cohorts of users who will be working together, this can be very useful as they will be able to learn and practice together. 


Suggested change

One vital aspect is that training should be targetted only at individuals who are going to be adopting the Git workflow very soon, or who are already adopting it. This means that what they have learnt can be applied straight away, removing the danger of knowledge atrophying during use. Related to this, if you can train cohorts of users who will be working together, this can be very useful as they will be able to learn and practice together.

One vital aspect is that training should be targetted only at individuals who are going to be adopting the Git workflow very soon, or who are already adopting it. This means that what they have learnt can be applied straight away, removing the danger of knowledge deteriorating prior to use. Related to this, if you can train cohorts of users who will be working together, this can be very useful as they will be able to learn and practice together.

frostwix · 2026-07-17T14:39:16Z

This chapter is quite good and touches upon many challenges in change management. There is some great advice here :)

aassuied-ps added 4 commits May 4, 2026 14:37

Delete site/assign.png:sec.endpointdlp

6212bee

Delete site/branch.png:sec.endpointdlp

8f7f48b

Update Challenges.qmd

3ca4840

Add an introduction and a plan.

Update Challenges.qmd

fff33d1

talk about tools

aassuied-ps linked an issue Jun 3, 2026 that may be closed by this pull request

Change management and git #50

Open

some proposed changes

00839b6

martiki9 added 3 commits June 26, 2026 14:44

fix stub

634f13a

make benefits a stub article for now

96a229d

remove erronously commited file

2875eb0

frostwix reviewed Jul 1, 2026

View reviewed changes

kieranjmartin and others added 7 commits July 10, 2026 10:16

Update white-paper/Challenges.qmd

631b54d

Co-authored-by: frostwix <154441859+frostwix@users.noreply.github.com>

Update white-paper/Challenges.qmd

091c130

Co-authored-by: frostwix <154441859+frostwix@users.noreply.github.com>

Update white-paper/Challenges.qmd

2c47e1f

Co-authored-by: frostwix <154441859+frostwix@users.noreply.github.com>

Update white-paper/Challenges.qmd

bc8735d

Co-authored-by: frostwix <154441859+frostwix@users.noreply.github.com>

Update white-paper/Challenges.qmd

e625214

Co-authored-by: frostwix <154441859+frostwix@users.noreply.github.com>

reword unclear sentence

1d60b76

Update white-paper/Challenges.qmd

2f4ad61

Co-authored-by: frostwix <154441859+frostwix@users.noreply.github.com>

frostwix reviewed Jul 17, 2026

View reviewed changes


		The Change Curve is a well known model for understanding how employees resond to change @HOLDSWORTH2024254. While there are many different implementations of it, generally speaking it is understood to be split into two main phases, first of resistance and then of acceptance. An important attitude in any company trying to make any sort of change, be it organisational or technological, is to have empathy for those individuals who are experiencing it, and give them the support they need.

		We must understand that any change will take time to embed into an organisation, and the main thing we can influence is how fast that change goes, and how well we can adopt the technology.


		## The Change Curve

		The Change Curve is a well known model for understanding how employees respond to change @HOLDSWORTH2024254. While it has many different forms, it generally begins with initial shock, followed by resistance, low morale, gradual experimentation, and then acceptance and integration. An important consideration for any company trying to make any significant change, be it organisational or technological, is to have empathy for those individuals who are experiencing it and give them the support they need.


		Depending on your company's size and how they want to use Git, there a number of tools to interact with Git and Github. These are covered more in the [appendix](tools.qmd), but your decision is likely to be motivated based on how close you want users to interact with Git.

		You may decide that you wish to abstract users access to Git or you might decide that you wish to get users comfortable with direct Git terminal access. Different tools will enable different approaches.

	You may decide that you wish to abstract users access to Git or you might decide that you wish to get users comfortable with direct Git terminal access. Different tools will enable different approaches.
	You may choose to hide Git's complexity from users by giving them easy-to-use tools, or you may choose to teach users to work directly with Git commands in the terminal. The tools you select will influence which approach is possible.


		There are a number of excellent resources for learning Git online. This means that when creating internal documentation on Git it is important to focus on how your organisation will be using Git in practice.

		Your documentation should focus first on the ways someone will work in their day to day, covering the typical flow and where possible integrating it into the tools they are likely to use. Documentation should be easy to access and use, and easy to search. We recommend where possible to not include this level of documentation in GxP training, as the latter is likely to be in systems that can be harder to update quickly based on user feedback.


		Your documentation should focus first on the ways someone will work in their day to day, covering the typical flow and where possible integrating it into the tools they are likely to use. Documentation should be easy to access and use, and easy to search. We recommend where possible to not include this level of documentation in GxP training, as the latter is likely to be in systems that can be harder to update quickly based on user feedback.

		GxP training is of course important to meet our compliance requirements, but we can normally build training on top of it which enables more dyanmic updates as you get feedback from users on what works and what does not.


		### Failure cases

		An important resource to build over time is how to resolve issues that might occur when using Git. The exact nature of the issues are likely to run into will be specific to your organisations workflow but some likely common issues are


		Where possible trainings should be live, and in person if it is possible to arrange, to allow maximum engagement.

		One vital aspect is that training should be targetted only at individuals who are going to be adopting the Git workflow very soon, or who are already adopting it. This means that what they have learnt can be applied straight away, removing the danger of knowledge atrophying during use. Related to this, if you can train cohorts of users who will be working together, this can be very useful as they will be able to learn and practice together.

Uh oh!

Conversation

aassuied-ps commented Jun 3, 2026

Uh oh!

kieranjmartin commented Jun 26, 2026

Uh oh!

frostwix left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

frostwix left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

frostwix commented Jul 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants