Row 30013

Row ID: 30013 | Dataset Entry | Axioma AXP Content Repository

Content Data

This page contains data entry 30013 from the Axioma AXP content repository. The structured data below represents the complete record for this entry.

Here a couple of tips for you to improve:

* Put a lot of emphasis on your comms. Like double or triple down on it. * Read others' work, internal and external, DS related and non-DS related. This will help you to understand how great story telling look like. When your team members or anyone presents try to understand what worked well and what didn't, for yourself and by reading the audience * read books (storytelling with data for example) * incorporate what you've learnt like that and make conscious decisions about what worked and what didn't and iterate * get feedback and try to get mentored by people that are great communicators (I. E. I worked closely together with an internal consultant to improve my and my team's presentation skills including plotting). * always try to get better

I'm managing people for a while now and this is a skill that I more often than not have to double down in with new hires. So you asked a highly relevant question.

Lastly a couple of general tips for storytelling: * ask yourself who your audience is and what's most relevant for them. How will they use it? What's the business value of your work? * write a story with a clear call to actions and name the teams that in your opinion can or should own the action. Keeo it easy to understand and efficient - no one wants to desipher your message or go through technical details before getting to the meat of your message. * Keep it as simple as your audience needs it. * plot for purpose and remove unnecessary clutter. Plots should be self expainatory even when embedded in text. Make em simple and use the title for the point you want to make. The subtitle can be used to add any necessary description. * are you presenting? Is this a write up? What you show should be also aligned with the type of comms. * manage the audience's cognitive load wherever you can. The focus should always be on your main points. * be opinionated. You are the expert. You are expected to have an opinion based on the work you did. * adjust your write up multiple times until you are really convinced that someone with way less context than you understands your intention. * always keep it friendly but don't shy away from pointing out results that are concerning. Those are most often the most interesting ones and have the potential to initiate change. That's actually the reason why you get paid. To change things for the better :)

Those are just a few points and sorry that the above isn't very structured. I hope helps tho.

FieldValue
text Here a couple of tips for you to improve: * Put a lot of emphasis on your comms. Like double or triple down on it. * Read others' work, internal and external, DS related and non-DS related. This will help you to understand how great story telling look like. When your team members or anyone presents try to understand what worked well and what didn't, for yourself and by reading the audience * read books (storytelling with data for example) * incorporate what you've learnt like that and make cons…
label r/datascience
dataType comment
communityName r/datascience
datetime 2024-05-21
username_encoded Z0FBQUFBQm5Lak1GRGRIbER5TkI1TjcyLU52Q3JkRlBrNDNYRF9YOVhIYTNDVGdFclJNdnVyRHJqREN2aFVfd3ZYaVBCdHVjc210dTJ6UVV2SUpyVzJrdFFXSndyQVpvenc9PQ==
url_encoded Z0FBQUFBQm5Lak9WWF9xSUprNTl6RGEtaUpHNVR3cmU3NlNaQ1hSUUp6VW9UckktNkpnYndlV0hKWHY3Z3h2UV9WQ1ByaGkyRWp1d1VvQk1FbGVxRkpES0FRVXB6VTBKdFBCZVFjczBmQk51bkVZNDUzOWV5ZTBnZnpIZ0JJSjFpOFdsSWFYNXNxVVhESmliVmQ2cXI0WnRpb1UwU3BBdmNKdFU1aVRJOHBrQ2sxb0RoMlk1ZlZhaE1EM3NJdDJWUnpaRXJNYUNwSW55X2VjM0pwdFg0a0Nhcm1BVmk4MGlrUT09

Raw Record

{
  "text": "Here a couple of tips for you to improve:\n\n* Put a lot of emphasis on your comms. Like double or triple down on it.\n* Read others' work, internal and external, DS related and non-DS related. This will help you to understand how great story telling look like. When your team members or anyone presents try to understand what worked well and what didn't, for yourself and by reading the audience\n* read books (storytelling with data for example)\n* incorporate what you've learnt like that and make conscious decisions about what worked and what didn't and iterate\n* get feedback and try to get mentored by people that are great communicators (I. E. I worked closely together with an internal consultant to improve my and my team's presentation skills including plotting).\n* always try to get better\n\nI'm managing people for a while now and this is a skill that I more often than not have to double down in with new hires. So you asked a highly relevant question.\n\nLastly a couple of general tips for storytelling:\n* ask yourself who your audience is and what's most relevant for them. How will they use it? What's the business value of your work? \n* write a story with a clear call to actions and name the teams that in your opinion can or should own the action.\nKeeo it easy to understand and efficient - no one wants to desipher your message or go through technical details before getting to the meat of your message.\n* Keep it as simple as your audience needs it.\n* plot for purpose and remove unnecessary clutter. Plots should be self expainatory even when embedded in text. Make em simple and use the title for the point you want to make. The subtitle can be used to add any necessary description.\n* are you presenting? Is this a write up? What you show should be also aligned with the type of comms.\n* manage the audience's cognitive load wherever you can. The focus should always be on your main points.\n* be opinionated. You are the expert. You are expected to have an opinion based on the work you did.\n* adjust your write up multiple times until you are really convinced that someone with way less context than you understands your intention.\n* always keep it friendly but don't shy away from pointing out results that are concerning. Those are most often the most interesting ones and have the potential to initiate change. That's actually the reason why you get paid. To change things for the better :)\n\nThose are just a few points and sorry that the above isn't very structured. I hope helps tho.",
  "label": "r/datascience",
  "dataType": "comment",
  "communityName": "r/datascience",
  "datetime": "2024-05-21",
  "username_encoded": "Z0FBQUFBQm5Lak1GRGRIbER5TkI1TjcyLU52Q3JkRlBrNDNYRF9YOVhIYTNDVGdFclJNdnVyRHJqREN2aFVfd3ZYaVBCdHVjc210dTJ6UVV2SUpyVzJrdFFXSndyQVpvenc9PQ==",
  "url_encoded": "Z0FBQUFBQm5Lak9WWF9xSUprNTl6RGEtaUpHNVR3cmU3NlNaQ1hSUUp6VW9UckktNkpnYndlV0hKWHY3Z3h2UV9WQ1ByaGkyRWp1d1VvQk1FbGVxRkpES0FRVXB6VTBKdFBCZVFjczBmQk51bkVZNDUzOWV5ZTBnZnpIZ0JJSjFpOFdsSWFYNXNxVVhESmliVmQ2cXI0WnRpb1UwU3BBdmNKdFU1aVRJOHBrQ2sxb0RoMlk1ZlZhaE1EM3NJdDJWUnpaRXJNYUNwSW55X2VjM0pwdFg0a0Nhcm1BVmk4MGlrUT09"
}
Explore Dataset Explore Row

Entry Information