Updated abstract

[abikesa]

Comments transcribed from J in the .docx file

Digital transformation projects often face a common challenge: low success rates. Globally, IT professionals have become resigned to considering project failure as virtually inevitable. However, there's a notable distinction in the trend between developed and developing economies. Developed economies show a tendency toward a reduction in digital transformation failure rates, while in developing economies like Uganda, these rates persistently remain high.

• Digital transformation projects

  • Should digital transformation be defined in the Abstract, or is that saved for the introduction?

• This opening paragraph is so solid and coherent. So easy for the reader to comprehend what the problem at hand is.

---

In the dynamic global educational landscape, Government of Uganda, through Technical and Vocational Education and Training (TVET) institutions, actively promotes integrating digital technology to enhance skills. However, the harsh reality is that approximately 70% of digital transformation projects worldwide fail, resulting in substantial financial losses. To put it in perspective, this equates to a loss of UGX 9.9 million for every UGX 1 billion invested in these projects. This study delved into digital transformation projects in Uganda that encountered comparable challenges.

• Replace the highlighted phrase with The
• enhance skills:
  • Can we be more specific on the skills being referred to here. I assume these are skills aimed at improving the success rate of digital transformation projects?
• 70% of digital transformation projects
  • Do we know the failure rate in developing economies - to give more perspective to the Ugandan context?

---

One primary reason for these failures is the lack of process quality control, which is deeply intertwined with the inadequate implementation of IT governance. This issue remains a significant obstacle to successfully executing digital transformation projects, particularly in developing economies like Uganda.

• I added control to emphasize the point.

---

Traditional approaches and established frameworks have shown their limitations in addressing this pervasive challenge. A potential solution lies in embracing the principles advocated by agency theory. These principles emphasize the need for controls and checks to ensure agents act in the best interests of principals. This includes meticulous monitoring and the enforcement of quality standards, which are essential for ensuring that processes meet the required level of quality. This underscores the importance of maintaining organization-wide oversight when extensive simultaneous changes are impractical.

• Traditional approaches and established frameworks
  • of what?
  • Digital transformation projects?
• This underscores the importance of maintaining organization-wide oversight when extensive simultaneous changes are impractical.
  • This sentence isn't intuitively clear to me, especially the link between the latter half of the sentence to the first bit. Are extensive simaultenous changes mutually exclusive from organization-wide oversight?

---

To this end, this study introduces a specialized "Framework for Improved Success of Digital Transformation Projects" tailored to meet the specific requirements of TVET institutions in Uganda. The primary objective of this framework is to reduce the high rate of project failures and cultivate an environment conducive to the success of digital transformations.

• Substituted address these challenges with this end

---

Accordingly, this study has three key objectives: i) Identify the critical components for a successful digital transformation framework in Ugandan TVETs; ii) Develop a fitting framework designed to accommodate the unique context of Ugandan TVETs; iii) Evaluate the effectiveness of the designed framework for digital transformation in Ugandan TVETs.

• Inserted Accordingly

[abikesa]

Hey P,

I hope Sarah and J can learn to use GitHub. You too. Wayyyyy neater than email. It was specifically designed for collaboration by the worlds most successful collaborators (i.e., Microsoft, Apple, Linux, etc)

So I've done above what I hope J will be able to do next time: make comments directly to GitHub.

Now my comments:

1. Abstract is sooooooooo readable
   • Use this link to update the abstract so that we give you further feedback going forward
   • No worries about version control: GitHub takes care of the history
   • Just use a commit statement each time you update the version
   • Always use the same name (i.e., not _version2 or _Oct_29_2023.docx)
2. Its 550 words long, which is perhaps 200-300 words too many
3. Varies with field, but abstract just means that: a super-tight summary of everything
4. You'll have to decide what "self-imposed rule" you use here
5. My intuition is that 500 is too many words: an abstract should never be more than 4 paragraphs
   • Background
   • Methods
   • Results
   • Conclusion

As such, to be able to assess the abstract, one needs to know the entire thesis. Here's my attempt to do so over 6 hours on Saturday!!!

Lets discuss via a zoom call one of these weekends?

[DrSarah23]

I agree with the above comments. My only issues remain: 1. How did you arrive at the suggested"Framework for Improved Success of Digital Transformation Projects"; 2. Abduction or deduction, talk about the design and how your results revealed a framework or guide; 3. Or was it the research question that led to this? I still need to read the full paper to make sense of these questions.