First cut of the Data Practitioner Persona Examples.
Good start, they will need a bit of iterating until they are good enough for the final book.
ChatGPT has been pretty good at generating the Avatars for these once I got the Prompts about right.
Not sure if I should add an Analytics Engineer into the mix for the standard Data Practitioner Personas, I think the fact I didn’t add it straight off is my answer for this one.
I am tempted to add one more area / diagram in the template, a T-Skills diagram for the Data Practitioner persona type and the same format of diagram but Business Units for Information Consumers.
Do I find a space to add it or do I replace one of the other area with it.
IT will be the only area that changes depending on the Persona Type is this a good or a bad thing?
Do I align the diagram with the Information Value Stream so its consistent across all Persona Types.
Brain dump of the feedback I have got from people kind enough to spend the time to give me some on these draft, feel free to send me your feedback if you have some.
In some orgs the Data Engineer and the DataOps Engineer are the same Persona
Add a Data Architect prefix persona
Need to add a comparison between Data Analyst and Data Scientist
There is not enough differentiation on the Engage Bars across the Data Practitioner personas.
Need better differentiation in the Actions text vs the Work to be Done text
Data Scientist persons seems end-to-end when often that persona just works on the “Jupyter Notebook” part of the Information Factory.
Data Quality should be added in somewhere.
BI Developer persona is a legacy persona, based in large orgs or legacy tools, that data work is done by the Analysts in modern orgs / tools.
No posts
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.