Tag: Use Cases

As part of Culture Kent’s research, we asked Deeson to provide us with Personas & Use Cases for the types of users that will potentially use our Events open data source. In turn, they identified six Personas and explained their corresponding Use Cases. This series of blogs will highlight each one in detail according to their behaviour & motivations or responsibilities, goals, challenges, and interests.

In this post, we discuss another Persona & Use Case, the ‘Problem Solver’, the sixth type of user who will potentially use our Events open data source. The ‘Problem Solver’ is someone who might be self-employed want wants to take their kids to more Arts & Cultural events, yet the information is not easily accessible for someone who is busy. This person is very motivated and able to pool resources together and working collaboratively.

People who are Problem Solvers’ might state:

“I just love taking on projects and solving problems, especially when I can relate to them.”

What are their responsibilities?
• Developing ideas based on real world problems
• Building relationships and pooling resources to get things done
• Researching users to better understand the problem they are trying to solve

What are their goals?
• Build a legacy! They want to see their ideas grow and expand
• Gain outside investment to keep developing their ideas
• Fill gaps in the market with great solutions

What are some of the challenges they face?
• Building accurate and timely content to make solutions valuable
• Finding time relevant partners takes a lot of time
• Data integrity – how can I be sure data I’m being given is correct?
• Data in a common format and structure to make it easy to integrate

What are they interested in regarding an open data source?
• Data feeds that allow them to focus on developing a better solution
• A common data structure for events
• Opportunities to monetise their solution
• Giving credit to partners
• Open and honest collaboration

Does this sound like you or someone you know? Leave a comment to discuss!

This post is made possible by the work done by Deeson in Canterbury, Kent. We truly appreciate their hard work and collaboration with Culture Kent.

Like this:

As part of Culture Kent’s research, we asked Deeson to provide us with Personas & Use Cases for the types of users that will potentially use our Events open data source. In turn, they identified six Personas and explained their corresponding Use Cases. This series of blogs will highlight each one in detail according to their behaviour & motivations or responsibilities, goals, challenges, and interests.

For the fifth type of user who will potentially use our Events open data source, we discuss another Persona & Use Case, the ‘Theatre Enthusiast’. The ‘Theatre Enthusiast’ is someone who might not only perform in a theatre, they might also be the owner, promoter, and accountant. Between practices, shows, and promoting their events, they do not have much time to do a great deal of research and marketing to increase audiences.

People who are ‘Theatre Enthusiasts’ might state:

“We’re good at engaging our ‘fans’, it’s attracting new audiences we struggle with”

What are their responsibilities?
• Day to day performance as an Accountant
• Organising and helping direct practice and live shows
• Marketing and promoting upcoming events in spare time

What are some of the challenges they face?
• Time, budget and resource – as a hobby this is even more strained
• Promoting to new audiences, unsure how to reach them
• Duplicate data entry across different promotion platforms

What are they interested in regarding an open data source?
• Expanding their audience
• Reducing duplicate data entry and therefore wasting time and resource
• Systems with simple data input

Does this sound like you or someone you know? Leave a comment to discuss!

This post is made possible by the work done by Deeson in Canterbury, Kent. We truly appreciate their hard work and collaboration with Culture Kent.

Like this:

As part of Culture Kent’s research, we asked Deeson to provide us with Personas & Use Cases for the types of users that will potentially use our Events open data source. In turn, they identified six Personas and explained their corresponding Use Cases. This series of blogs will highlight each one in detail according to their behaviour & motivations or responsibilities, goals, challenges, and interests.

In the fourth part of our series on the types of users who will potentially use our Events open data source, we discuss another Persona & Use Case, the ‘Event Marketer’. An ‘Event Marketer’ is an employee responsible for advertising events held by their organisation, or someone who owns or manages a venue that holds events, specifically a Cultural Marketing Manager. This person is in charge of increasing the event’s audience, an important task that depends upon spreading the word beyond their existing audience.

People who are ‘Event Marketers’ might state:

“Is there an opportunity to collaboratively work on getting event information out to a wider audience?”

What are their responsibilities?
• Working closely with schedules to plan marketing budgets and activity
• Promote and market events across the local area using a variety of methods
• Build good relationships with performers and support them in promoting themselves

What are their goals?
• Increase marketing activity reach to promote events to new audiences
• Increase attendances at events across all types; comedy, theatre, arts, etc.
• Enhance reputation as an inspiring arts centre and encourage community participation

What are some of the challenges they face?
• Limited marketing budget
• Targeting the correct audiences for the correct types of events
• Sharing commercially private data in a safe and non-damaging manner

What are they interested in regarding an open data source?
• Collaborating with other institutions who understand the problem the sector is facing to bring data together
• Getting ‘what’s on’ information out to a wider audience more easily

Does this sound like you or someone you know? Leave a comment to discuss!

This post is made possible by the work done by Deeson in Canterbury, Kent. We truly appreciate their hard work and collaboration with Culture Kent.

Like this:

As part of Culture Kent’s research, we asked Deeson to provide us with Personas & Use Cases for the types of users that will potentially use our Events open data source. In turn, they identified six Personas and explained their corresponding Use Cases. This series of blogs will highlight each one in detail according to their behaviour & motivations or responsibilities, goals, challenges, and interests.

In the previous two posts, we discussed two different types of users who will potentially use our Events open data source. In this post, we consider a third Persona & Use Case, this time the ‘Strategic Planner’. Here, a ‘Strategic Planner’ is anyone who plans events, such as an Events Schedule Director. This is someone who might rely on past statistics and audience feedback to improve upcoming events.

People who are ‘Strategic Planners’ might state:

“To have a coherent picture of what’s happening and where would help us plan more effectively”

What are their responsibilities?
• Scheduling and planning of events
• Developing income generation
• Audience development
• Building strategic partnerships
• Showcasing art & culture

What are their goals?
• Increase national and international recognition
• Transform Kent – people and places
• Position Kent as ‘culture county’
• Boost the local economy
• Increase community well-being

What are some of the challenges they face?
• Benchmarking against similar institutions
• Evidence based planning
• Resources – becoming more sustainable
• Reliability of data

Like this:

As part of Culture Kent’s research, we asked Deeson to provide us with Personas & Use Cases for the types of users that will potentially use our Events open data source. In turn, they identified six Personas and explained their corresponding Use Cases. This series of blogs will highlight each one in detail according to their behaviour & motivations or responsibilities, goals, challenges, and interests.

In the previous post, we discussed the Persona & Use Case for the ‘Culturally Curious’, the first of our six-part series on the types of users who will potentially use our Events open data source. In this post, we focus on the ‘Strategic Thinker’, which might be someone specific like an Arts Council Director, or, in a broader sense, someone whose role focuses on how Arts & Culture can assist with economic growth, lead to new skills, and increase community well-being.

People who are ‘Strategic Thinkers’ might state:

“By sharing information we’ll be able to become smarter as a sector, target funding and build a better offer for cultural tourists”

What are their responsibilities?
• Providing strategic direction for cultural growth to the local councils
• Understanding the relationships between arts, culture and local area benefit
• Identifying beneficial partnerships and making the connections

What are their goals?
• Grow the local economy by bringing in new businesses and tourism
• Support the creative industry by developing skills in young people
• Increase community well being to make peoples lives better through arts and culture

What are some of the challenges they face?
• Getting the data required to provide a high service level to local people
• Finance – the sector is just catching up with the impact of the recession
• Understanding how event data maps to other data sets about local well being

What are they interested in regarding an open data source?
• Better data mapping and visualisation tools
• An agreement between local organisations to share data for the benefit of the local area
• A picture of what events have happened, are happening, and are planned for the future to
help target funding to the right areas

Does this sound like you or someone you know? Leave a comment to discuss!

This post is made possible by the work done by Deeson in Canterbury, Kent. We truly appreciate their hard work and collaboration with Culture Kent.