Erik SunReferences

Making Room

Learning to build shared understanding

I bring structure and reliability to collaboration. These artefacts trace how I began examining the assumptions behind those strengths, testing different practices, and asking whose knowledge actually changes our shared work.

Week 1 · Padlet

What I counted as success

I chose this Padlet because I was proud of what we built at FutureFocus. Reading it again complicates the story I told in A1: my teammate and I discussed designs and compared tradeoffs, so calling it merely coordination was too sweeping. Bedwell et al. (2012) place reciprocal engagement at the centre of collaboration. That shifts my attention towards how our decisions developed and whether either of us could reopen them as implementation progressed. I still value efficient delivery. This artefact reminds me to examine the process fairly, including when my own self-critique becomes more confident than the evidence allows.

Week 2 · Values and inequality

Putting my values under examination

I still believe effort and competence matter. This map made me question how readily I assume they are recognised fairly. We connected inequality to education, geography and inherited advantage, yet agreeing on those connections did not mean we had examined our own assumptions. Argyris (1994) makes self-examination part of learning. My reflection records trying to listen before solving, then returning to task completion as time ran out. That tension feels familiar: I can value openness while making progress my immediate priority. I now want to ask whose experience is missing before helping a group settle on its explanation.

Week 3 · Working styles

When coherence arrived too early

Preparation and logical organisation felt like reassuring strengths on our working-style board. Overthinking and inflexibility were less comfortable to recognise. During the creativity exercise, I helped refine our argument about AI and inequality until we ran out of time. Making the idea coherent had absorbed the space for alternatives. The Double Diamond separates expanding possibilities from focusing them, while allowing us to revisit earlier decisions (Design Council, n.d.). I see its value in questioning my timing: when am I helping an idea develop, and when am I closing down the search? Our later healthcare disagreement gave me an opportunity to practise staying open longer.

Week 4 · Social-isolation pitch

Explaining what makes a proposal worthwhile

A budget, attendance target and evaluation plan made our networking proposal feel convincing to me. Having helped establish an engineering student association, I was drawn to making an initiative workable. Boltanski and Thévenot (1999) help explain that preference through industrial worth, which values efficiency and organisation. But attendance would tell us little about whether an isolated student felt able to join. That question introduces a different basis for judging the proposal: inclusion. I keep this board because it makes my priorities visible. Before defending a practical plan, I need to understand how the people it is intended to help would judge its value.

Week 5 · Charter retrospective

Testing our charter against our practice

Our charter promised shared learning. Yet our retrospective recorded equal contribution and mutual respect alongside concerns that task progress had displaced thinking together. I recognise my own habits in this discrepancy: delegating responsibilities feels productive, but completing individual tasks does not necessarily create collective understanding. Argyris's (1994) distinction between espoused theory and theory-in-use exposes that gap. Okhuysen and Bechky (2009) similarly identify common understanding, alongside accountability and predictability, as essential to coordination. I had focused disproportionately on the latter two. I now see that effective progress meetings should examine how individual contributions inform one another, rather than simply whether assigned work is finished.

Week 6 · Personal reflection

Recognising the signals I send

Under pressure, I speak faster, narrow my attention and sometimes go quiet when I am stuck. I had understood that silence as keeping my stress contained. Barsade’s (2002) research on emotional contagion made me consider how my mood might still enter the room. The laboratory findings cannot tell me how my teammates experienced me, but they give me a reason to question my assumption. My reflection records beginning to slow down and name uncertainty. That feels more useful than trying to appear composed throughout: it gives others something they can respond to. I still need to notice whether my behaviour actually makes approaching me easier.

Weeks 7–8 · Devising and storyboard

Testing an idea with other people

The devising workshop revealed how differently people interpreted the same gesture. That became relevant when we replaced a vague AI-assisted interpreter flag with a phone-interpreter scene. As a script contributor and actor, I saw the idea emerge through discussion, performance and the constraints of our mockumentary format. Glăveanu (2010) situates creativity within relationships between people and artefacts, challenging my tendency to prioritise refining an initial proposal. Yet our feedback exposed another difficulty: individually effective scenes did not necessarily form a coherent narrative. West (2002) distinguishes creativity from its successful implementation. I learnt that openness generates possibilities, but collaborative judgement must connect them into something meaningful.

A2 · Storyboard and feedback

Making small changes work together

I initially favoured revised reception and triage forms because they seemed achievable. A teammate wanted a more effective, systemic response. I voiced my concerns, invited alternatives and suggested involving Chelsea from Belvoir. Our proposal grew to include doctor training and greater interpreter availability. That changed what I considered sufficient: identifying a need only helps if the service can respond. Yet our storyboard feedback exposed another gap: Saksham could comment while staff retained control of the pilot. Arnstein’s (1969) distinction between consultation and decision-making power helps me examine that limitation. The civic-planning framework raises a useful question here: whose contribution actually changes the design?

Week 10 · Group retrospective

Evaluating how we actually worked

Zoom meetings, pre-seminar stand-ups and WhatsApp helped us coordinate, while feeling comfortable proposing uncertain ideas encouraged my participation. Edmondson (1999) associates psychological safety with team learning, although my experience cannot establish whether everyone felt equally safe. Yet openness did not eliminate the challenges of interdependence. Scheduling clashes left Wednesday as our only viable filming day, requiring us to adapt our production and rely more heavily on talking-head scenes. Okhuysen and Bechky (2009) identify accountability, predictability and common understanding as foundations of coordination. I realised that psychological safety and operational reliability serve different, complementary purposes. At Optiver, I would seek earlier checkpoints and make dependencies explicit before they become constraints.

Collaboration Statement · Peer feedback

Letting another perspective change my statement

Kris's feedback challenged a phrase I had felt confident about: taking responsibility together. He valued my emphasis on openness but questioned how different perspectives would translate into decisions and ownership. Bedwell et al. (2012) emphasise reciprocal engagement towards shared goals, while Okhuysen and Bechky (2009) identify accountability as essential to coordinating interdependent work. His feedback exposed what my statement had left unresolved: participation does not automatically establish responsibility. I began this semester equating good collaboration with reliable delivery. I now understand reliability more broadly: creating space for different perspectives, allowing them to influence decisions, and ensuring those decisions lead to clear ownership. Revising my statement tested whether I would practise that openness myself.

The whole picture

Start again ↑
References
  1. Argyris, C. (1994). Good communication that blocks learning. Harvard Business Review, 72(4), 77–85. https://hbr.org/1994/07/good-communication-that-blocks-learning
  2. Arnstein, S. R. (1969). A ladder of citizen participation. Journal of the American Institute of Planners, 35(4), 216–224. https://doi.org/10.1080/01944366908977225
  3. Barsade, S. G. (2002). The ripple effect: Emotional contagion and its influence on group behavior. Administrative Science Quarterly, 47(4), 644–675. https://doi.org/10.2307/3094912
  4. Bedwell, W. L., Wildman, J. L., DiazGranados, D., Salazar, M., Kramer, W. S., & Salas, E. (2012). Collaboration at work: An integrative multilevel conceptualization. Human Resource Management Review, 22(2), 128–145. https://doi.org/10.1016/j.hrmr.2011.11.007
  5. Boltanski, L., & Thévenot, L. (1999). The sociology of critical capacity. European Journal of Social Theory, 2(3), 359–377. https://doi.org/10.1177/136843199002003010
  6. Design Council. (n.d.). Framework for innovation. https://www.designcouncil.org.uk/resources/framework-for-innovation/
  7. Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. https://doi.org/10.2307/2666999
  8. Glăveanu, V. P. (2010). Paradigms in the study of creativity: Introducing the perspective of cultural psychology. New Ideas in Psychology, 28(1), 79–93. https://doi.org/10.1016/j.newideapsych.2009.07.007
  9. Okhuysen, G. A., & Bechky, B. A. (2009). Coordination in organizations: An integrative perspective. Academy of Management Annals, 3(1), 463–502. https://doi.org/10.1080/19416520903047533
  10. West, M. A. (2002). Sparkling fountains or stagnant ponds: An integrative model of creativity and innovation implementation in work groups. Applied Psychology, 51(3), 355–387. https://doi.org/10.1111/1464-0597.00951
AI acknowledgement

OpenAI Codex was used to review the supplied materials, organise and draft annotations, identify relevant literature, check wording and referencing, and build and test the website. The personal experiences come from my own artefacts, reflections, and clarifications. I remain responsible for verifying the claims and references and revising the final submission to represent my own experience and judgement.

Download the annotation script