---
# System prepended metadata

title: Lead DS responsibilities in So

---

## Lead DS responsibilities in SoCaR/UA 2.0

General questions:
- Scheduling meetings among us three
- Aim to review after first month (e.g. eof Jan)?


Proposed:
- Stuart: 1, 2, 3, (4), (8), 9, 11
- Sam/Andy: (2), (3), 4, 5, 6, 7, 8, (9), 10, (11)

| Area | Approx time comitment | Stuart |  Andy | Sam |
|-|-|-|-|-|
| 1. Leadership meetings | 0.1  |  x  | (x)   |  (x)   | 
| 2. E&S Mission dev     | 0.1  |  x  | (x)   | (x)  |
| 3. Internal/external stakeholders, UATP promo | 0.1  |  x  | (x) | (x - interaction with weekly?)  |
| 4. UATP 6 month cycle features/planning (coordinating the updating) | 0.2-0.3  |(x)  |  (x)  |  x  |
| 5. Allocating REG people | 0.0  |    | review in April | review in April |
| 6. Weekly/monthly in-person   | 0.05-0.1  |    | monthly   |  weekly   |
| 7. clim-recal work  | FTE estimate is requested by Monica (PM) - GM spent ~0.2 FTE   |    | x    | (x) |
| 8. Mentoring/growth/pastoral for REG    |  0.  |(x)  | x - review in April, -> 7   |    |
| 9. UATP development (connects to 4)  |  0.1     |  x  |  (x - e.g. meetings)  |  (x - e.g. meetings)   |
| 10. Interface with REG for work requirements  | 0.1   |    |  (x)   | x |
| 11. LM of PDRAs    | 0.0  |  x  |  (x)   | (x)  |


1) Participating in the leadership meetings and decisions as a co-I and platform lead, including strategic decisions around how the work fits within the Turing landscape, E&S, TRIC, etc, recruitment, Group Leads (GL) connections, priorities for the future, collaborations, etc. Main collaborators: Mark, Dani, Kelin, Mariam, Jen, GLs, Partnerships.

Lead: Stuart
Meetings: alternating bi-weekly (1 internal, 1 external)
Example tasks: Meetings produce a few hours of work typically, e.g. recruitment tasks, delegation of tasks, documents that need to be shared, REG input to grant proposals, organising a new set of talks on team developement.

Questions:
- Do Sam and/or Andy need to attend these - everyone or just occasionally? 
    - GM: No in the first instance. It is good to have just one person responsible for this. 
- Is co-I and platform lead still need to be same person?
    - GM: No, none of the three of you will be co-I as far as I know - sorry, I wrote this describing my own role.

2) Co-shaping the sustainable cities E&S mission, representing both SoCaR and REG perspectives/interest/priorities. Main collaborators: Mark, Dani, GLs, Jen, Alden, Eric, Scott.

Lead: Stuart with Sam & Andy
Meetings: 2 monthly meetings
Tasks: Meetings plus conversations that happen after

Question: Do Sam and/or Andy need to attend these - everyone or just occasionally?
    - GM: One of these meetings is on WS2.4 ie climate work. I think it makes sense for Andy to attend this one given he is involved in clim-recal. Stuart should attend too. I will email Harry to add you both.

3) Developing links with stakeholders/collaborators/clients/funders within and outside the Turing, platform promotion, etc in collaboration with RAM, AIUK, E&S, other REG people in E&S, various meetings. Main collaborators: Mark, Dani, Jen, Eric, Scott, GLs.

Lead: Stuart with Sam & Andy
Meetings: flexible
Tasks: Conversations and prep for events, meetings

Question: Do Sam and/or Andy need to attend these - everyone or just occasionally? Some of these will be more specific to co-I/platform lead?
    - GM: There is no specific meeting attached to (3) at the moment. But some might need to be created e.g. we discussed a REG meeting across E&S when we last met, also conencting researchers across E&S according to needs. Any of you could attend these as required/appropriate. Similar with partners and external collaborators. 

4) Scoping/organising/prioritising the pipeline of features/projects that feed into the UA Technology platform. Managing the 6-monthly cycles. Defining ways of working for the team. Main collaborators: Mark, Dani.

Lead: Sam & Andy with Stuart
Meetings: organising monthly in-office, weekly stand-up
Task management of the UATP project board / issues
Tasks: Github management, issues, meetings organisation and running

Planning and coordinating:
- Labels for issues
- Project board add gantt chart
- Who's responsible for maintaining each project (assignment?) that's part of platform


5) Allocating REG people to the various work streams, combining project priorities with individual preferences and development goals.

Lead: Sam & Andy
Meetings: 
As required
Tasks: As required

6) Bringing the community together in weekly meetings, monthly in-person events, co-working sessions, slack etc.

Lead: Sam & Andy
Overlaps with 4
Tasks: managing calendar and invites, agendas

7) Managing Griff's and Bowen's work in clim-recal and contributing code to the project. Main collaborators: Griff, Bowen, Monica, Ruth, Jen.

Lead: Sam & Andy
Meetings: Weekly project update, work managed by Monica mostly
Tasks: Discussion on project direction, managing day to day work, co-working, monitoring progress, writing reports, individual contribution, reviewing code

8) Mentoring/growth/pastoral care of more junior REG members and researchers. Represent REG members' needs and interests at UA daily work and leadership meetings.

Lead: Sam & Andy with Stuart
Meetings: ad hoc
Tasks: Meetings, ad hoc help

9) What is the platform - iterative definition that will continue into the future. Main collaborators: Mark, Dani, GLs.

Lead: Stuart with Sam & Andy
Meetings: ad-hoc discussions and monthly meetings etc
Tasks: Organising sessions for the team to discuss, documenting discussions

Question: We think that both Sam and Andy should be in the loop on this (eg attend relevant meetings as required).
    -  GM: I agree, everyone should contribute to this and be in the loop. Hopefully the main mechanism to drive this forward can be the monthly meetings but also I expect some things will come organically from the work streams and informal conversations. Stuart could take the role of coordinating and bringing everything together if that helps.

10) Interfacing with REG and supporting scoping of new UA requests. Negotiating on both sides to add new people when needed. Managing Forecast tool allocations. Main collaborators: Gabriel, Eric, James G.

Lead: Sam & Andy
Meetings: REG project appraisal meetings (monthly)
Tasks: Writing project briefs, participating in appraisal meetings, negotiating, updating forecast and github issues within REG repo

11) Potentially some line management of PDRAs.

Lead: Stuart with Sam & Andy
Meetings: as needed (weekly or every 2 weeks)
Tasks: Meetings mostly

Questions:
- What would REG's involvement in 11 this look like? eg REG's support for Anna Z atm, or Tim H. line management of a PDRA in LwM? Or coving for Stuart if anything arrises whilst Stuart is on-leave etc?
    - GM: This is unclear yet. It might not be needed but there was talk in the leadership team of potentially some LM from REG to some researchers if appropriate. At the moment nothing. I think it is more likely that GLs will take some LM responsibility when they are aligned better with the current work. Covering Stuart could be useful in some cases but temporary. 
- Is there an org chart for SoCaR as current/planned with GL changes?
    - GM: There is an org chart, I would recommend that Stuart asks Kelin/Mark in the next leadership meeting to share this across the team/put it in the github repo.