Loading…
Managing user knowledge across boundaries: the case for software startups to adopt user-centred design
Since the introduction of user-centred design (UCD), organisations have engaged with users to identify their needs and test key features to develop successful products. Software startups especially benefit from tacit user knowledge to create and validate their products in a resource-efficient way. H...
Saved in:
| Main Author: | |
|---|---|
| Format: | Default Thesis |
| Published: |
2021
|
| Subjects: | |
| Online Access: | https://dx.doi.org/10.26174/thesis.lboro.14602710.v1 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Summary: | Since the introduction of user-centred design (UCD), organisations have engaged with users to identify their needs and test key features to develop successful products. Software startups especially benefit from tacit user knowledge to create and validate their products in a resource-efficient way. However, tacit user knowledge can also cause challenges in undertaking UCD as it leads to syntactic (lack of information), semantic (lack of understanding) and pragmatic (lack of interest) boundaries between users, startups and their collaborators. The objective of the research is to explore how UCD Leads who work for startups could benefit from user knowledge across boundaries by adopting UCD with the aim of uncovering how software startups can succeed in new product development (NPD) in a resource-efficient way. To achieve the research objective and aim, the conceptual framework was abductively built to identify UCD Leads’ approach to manage current knowledge boundaries and boundary-crossing activities and to explore how they could adopt UCD to cross these boundaries. Qualitative data was collected in three phases via exploratory methods including participatory observations, semi-structured interviews, LEGO play sessions and document collection. The findings have revealed three key insights for software startups to succeed in NPD in resource-efficient, sustainable and less-biased ways. Firstly, products could be designed for, with and by users. To do this, software startups could pay attention to user experience, build user communities and undertake co-creation & co-design activities. Secondly, they could adopt an open innovation approach by acquiring expert knowledge via training & workshops and building partnerships, networks and intermediaries. Lastly, they could undertake adaptive planning of UCD: UCD processes could be automated and tailored, where resource capabilities for UCD could also be assessed. |
|---|