Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comms Pathway #69

Open
LizNeeley opened this issue Nov 21, 2024 · 6 comments
Open

Comms Pathway #69

LizNeeley opened this issue Nov 21, 2024 · 6 comments
Assignees

Comments

@LizNeeley
Copy link
Collaborator

LizNeeley commented Nov 21, 2024

Standing up a strategy & design plan for communications skills-building.

All development work identified in process happening in Workspace - Openscapes + Liminal - Comms Pathway

Purpose:

Mentors have requested skills-building. A haphazard approach introduces more cognitive load without providing clarity about why it's worth doing. This wastes energy and undermines enthusiasm. Comms skills are hard enough to acquire - we need all the clarity and dedication we can get.

Objectives:

a visible scaffolding that shows how each skill and concept fits into the whole and supports learners at any point in their own development, and in whatever domain they're drawn to first.

Process:

    • Confirm project management approach with Julie
    • Brainstorm relevant skills (in progress)
    • Map skills onto integrated framework (in progress)
    • Develop list of use cases and needs
    • Gap analysis of user needs
    • Build modules
    • Assess & iterate
@LizNeeley LizNeeley self-assigned this Nov 21, 2024
@LizNeeley
Copy link
Collaborator Author

LizNeeley commented Nov 21, 2024

  1. All development work identified in process happening in Workspace - Openscapes + Liminal - Comms Pathway
  • Openscapes Drive folder structure - where should I store project googledoc files? @jules32

  • Does it make more sense for me to have a separate repo for this project? I'm feeling like it would be better to have the process items as issues (e.g. this should be issue 1, not a comment in issue 69?

  • Will create new standalone repo and/or add new issues, do not need to add to Mainproject

@LizNeeley
Copy link
Collaborator Author

  1. Did a five min brainstorming sprint off top of my head, immediately remembered why this is so hard. Grabbed standing list I worked previously with AK, think it's worth revisiting and merging.
  • Create new tab
  • Revisit columns/coding
  • Merge/dedupe
  • Expand

@LizNeeley
Copy link
Collaborator Author

  1. Working theory is to try using Weick (2005) ESR as starting place

@jules32
Copy link
Contributor

jules32 commented Dec 2, 2024

Hi @LizNeeley ! I really like this Workspace Comms Pathway. Thank you. That table with skills, knowledge, affective is really great as a model to brainstorm from!

@LizNeeley
Copy link
Collaborator Author

@LizNeeley
Copy link
Collaborator Author

From 2024-12-19 co-working discussion, recognize a need to introduce power-mapping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: This Week In Progress
Development

No branches or pull requests

2 participants