The Consequence Gap

The calls for embedding soft skills in colleges have now become routine. Students, we are told, should graduate able to communicate, collaborate, adapt, think strategically, manage conflict, and work well with others. Yet, hiring managers and recruiters from industry would keep coming back and raise the issue about how new employees are often lacking in these areas.

It would be unfair to say that colleges do not teach these things at all. In fact, we do it quite extensively. Students learn the fundamentals of communication in writing and speaking courses. They practice presenting in technical courses. They are assigned group work where they are expected to collaborate. They complete larger projects that require some planning, some adaptation, some division of labor, and some strategic thinking. They learn the form of a professional email. They learn that meetings should have structure. On paper, much of the machinery is already there. What is still missing?

In this essay, I want to present my thoughts on three topics:

• Why do many students fail to fully internalize soft skills despite extensive exposure?
• How can capstone courses turn these skills from academic exercises into lasting habits?
• Is it possible to introduce meaningful versions of this earlier in the curriculum?

Weakness of consequences

I want to begin this section with my anecdotal observation on a Software Engineering Capstone (CSC402) course that I have taught every semester since Fall 2024. At the beginning, the motivation for this course was simply to provide students with an experiential learning experience by working on projects provided by external clients. As this is a course for seniors that are close to graduation, they are expected to come in with adequate technical preparation through previous electives. This course is not meant to be a gate keeper but to serve as a personal measuring stick: to see how much everyone can accomplish before stepping out to the real world. At the end of the semester, each group will present their work, not in class, but in a public setting, in front of invited guests (deans, parents, clients, other students, etc) and on a large stage.

The course has been a success, as per both students’ interests (the course fills within one or two days of registration, with many stay on the wait list) and their post-course evaluation. One thing that surprised me in their post-course evaluation is the fact that they praised the course for helping them improve in teamwork, communication, and related professional habits. I asked myself, did they not learn communication skills earlier? After talking with other students that are outside of CSC402, they all mentioned how they learned specific communication techniques in their speaking classes. Similarly, many upper-level technical courses include a team project in their syllabi.

As I stated at the beginning, students learn communication and other soft skills in pieces across different courses. In these settings, they practice the skills where the stakes remain mostly academic. A presentation is often still just a presentation for a grade. Group work is often just group work in the peculiar ecology of school, where one competent student carries the project, or a cluster of close friends works smoothly because friendship covers for poor process, or everyone learns the delicate art of pretending that equal contribution occurred. Adaptation happens, but usually only enough to satisfy the assignment. Strategic thinking appears, but often in rubric-shaped form. Conflict management is less about managing conflict than about avoiding it. Everyone is nice and everyone is agreeable. Problems are swept under the rug because the semester is short and the grade matters more than the health of the collaboration. In that environment, students are not failing to learn altogether. They are learning early forms of soft skills. However, early forms are not the same as internalized habits.

The power of real consequences in capstone

While grades in CSC402 are not the primary emphasis, the non-grade consequences seem to be more significant for students. Over past 3 semesters (Fall 24, Spring/Fall 25) since the course began being offered, all groups have been successful in meeting external clients’ requirements and creating deliverable end-products. Perhaps, the fear of not meeting a client’s demands in this class is being translated as not being successful in the real world. Or, perhaps, the internal drive to be as good as or even better than the other teams in front of one’s family and other strangers is a lot more motivating than doing just enough to not fail the class.

This is probably the key to my initial second question about why capstone matters. Not because it suddenly introduces soft skills from nowhere, but because it changes the conditions under which those skills operate. A capstone with an external client and a public showcase does something that much of the earlier curriculum does not. It makes these skills consequential. It puts students in a setting where communication and collaboration are no longer just performance for evaluation, but tools that actually shape the work. In this setting, lack of collaboration makes the work impossible, miscommunications are expensive and carry potential impact down the road. In general, it makes professional habits, or the lack of them, difficult to hide.

A student may learn in a communication course how to write a polite and professional summary email after a meeting. In class, that can easily feel like busy work, the sort of exercise that exists mainly to prove that someone somewhere values professionalism. Then the same student enters a capstone project, leaves a meeting with a client, does not send a summary, and a week later discovers that everyone remembers the conversation differently. As the client adds features as if they had always been discussed, the team realizes that a missing email was not missing paperwork but missing control and leverage for pushing back. Suddenly, the summary email is no longer classroom etiquette but a critical component in every team’s workflow.

This pattern is observed for other soft-skill components as well. For example, unlike a standard in-class technical presentation to just fellow students and faculty, CSC402 students discover that repeating technical details to the direct client liaison (who already knows them) is wasteful. Instead, they focus on accomplishments and forward-looking statements, especially when the liaison’s supervisor is present, since that might hypothetically secure further funding. They learn that, in a team, being agreeable is not the same thing as being collaborative, and being assertive and knowing how to professionally address confrontations is critical to the team’s dynamic and productivity. Adaptation does not simply mean changing plans to keep a grade intact but to responding to shifting expectations, new information, and external pressures without losing project coherence. In short, may not introduce these skills from scratch, but it creates the conditions under which earlier exposure becomes difficult to ignore and easier to internalize.

This leads to a more interesting observation. We can make the case that colleges do teach the fundamental aspects of soft skills. However, they are taught in forms that are too isolated or low-stakes to make students internalize these skills. In other words, students rehearse these skills without fully needing them.

Can we create realistic pressure earlier?

The above observation should not be surprising, as the same is true of technical knowledge. We generally accept that technical skills mature through actual usage, and trials and errors. Yet with soft skills, colleges often act as if one or two communication courses plus various forms of group projects should do the trick. The hope seems to be that these fragments will somehow assemble themselves into professional judgment by graduation. Sometimes they do, and often they do not. If the realistic consequences in CSC402 have contributed toward this successful assembly, then is it possible to do the same thing in earlier courses?

In taking a deeper look at CSC 402, we can see that its non-grading consequences include fear of disappointing a client and public performance in front of family/strangers. These have different motivational mechanisms: accountability to others and social visibility, respectively. However, in the setting of CSC 402, they don’t operate separately but reinforce each other: if the students are successful in their project, that leads to a level of confidence that will improve the public presentation. On the other hand, the inclusion of non-classroom entities in the public presentation component motivates students to be even more diligent in their work, because below average performance does not simply mean a bad grade but a public demonstration of incompetence.

Can this one-two combo be recreated in other classes. In my opinion, not in its entirety. To some extent, the capstone course has the advantage of having enrolling students at the peak technical and mental form just before graduation, with all the desires and motivations to go out and be successful in the real world and without the option to turn back (not without significant financial and time cost). A sophomore, faced with the prospect of public demonstration of incompetence, can just drop the class and switch major! Various aspects of this combo can be integrated into domain-specific courses at upper junior/rising senior levels, but they will require significant commitment from faculty and organizational investment from department. For example, instead of public presentation, an end-of-semester shared poster presentation among upper-level courses with projects could be an alternative, at smaller scale and lesser motivational impact. Individual reflections that require comments on one’s thought process and team members could be part of a project rubric, but that means faculty will need to spend more time providing detailed feedback, or they will not see that their reflections and thoughts are properly validated. More importantly though, these activities need to be clearly explained to students so that they don’t see them as yet another piece of busy work.

Conclusion

Students do not fail to learn soft skills because colleges never mention them. They are not able to internalize them because the curriculum often teaches them in fragments and practices them under conditions too weak to make them necessary. Capstone, especially with external clients and public showcase, changes that by attaching consequence to what had previously been academic form. It shows that communication, collaboration, adaptability, and conflict management are not accessories to technical education but part of what makes technical work hold together in the first place. In an ideal curriculum, capstone would not be the first place where these skills become consequential. In practice, however, it may be the most natural place for that transformation to occur, because it concentrates technical maturity, external accountability, and public visibility in one setting. Earlier implementations are certainly possible, but it will take effort from both faculty and institutions to make that happen. The question is not whether colleges teach soft skills. They do. The question is whether they are willing to make those skills necessary for, and therefore internalized by, students before the final semester.