By the end of this chapter, you will be able to:
Mastering these skills helps you improve services and support, making users happier and your work more effective in the real trade.
Gathering user feedback is a critical activity in software development, ensuring that applications meet the evolving needs of end users. In Kenya’s dynamic technology landscape, where user expectations and business requirements rapidly change, effective feedback collection enables developers to refine software solutions, enhance user satisfaction, and maintain competitive advantage. This chapter focuses on practical methods for gathering user feedback, emphasizing tools and techniques relevant to software developers supporting application users. Understanding these methods helps professionals at banks, county government ICT departments, and educational institutions to systematically capture user insights for continuous improvement.
Collecting feedback from end users requires deliberate planning and the use of appropriate tools tailored to the software environment and user context. In Kenya, software developers often work with diverse user groups across sectors such as healthcare, education, and finance, making adaptable feedback methods essential. This section explores two key approaches: surveys project work and form builders, both widely used in software development projects to gather actionable user input.
Surveys are structured questionnaires designed to collect quantitative and qualitative data from users about their experience with software applications. In Kenya's software development context, surveys can range from simple feedback forms distributed via email to comprehensive online surveys integrated within applications. The success of surveys depends on their design, deployment, and follow-up analysis.
Surveys provide a scalable way to gather user opinions, preferences, and pain points, essential for iterative software improvement. They help identify usability issues, feature requests, and satisfaction levels, guiding developers in prioritizing enhancements. For instance, a SACCO implementing a new loan management system may use surveys to assess if users find the interface intuitive or if transaction processing meets their expectations. Surveys also facilitate benchmarking user satisfaction over time and across user groups.
Creating survey questionnaires requires clarity, relevance, and brevity to encourage user participation and yield meaningful data. Questions should be specific to the software features or workflows under review and avoid technical jargon that may confuse non-technical users. Including a mix of closed-ended questions (e.g., rating scales) and open-ended questions allows quantifiable analysis and detailed user comments. For example, a county government’s payroll system survey might ask users to rate system reliability and describe any encountered errors.
Surveys can be distributed through multiple channels depending on the user base and context. Online survey platforms like Google Forms or SurveyMonkey are commonly used for quick deployment and automated data collection. In environments with limited internet access, printed questionnaires or telephone surveys may be necessary. At a retail business using a POS system, developers might deploy surveys via SMS links immediately after transactions to capture timely feedback.
Once collected, survey data must be systematically analyzed to extract actionable insights. Quantitative responses can be summarized using statistical measures such as averages and frequency distributions, highlighting trends in user satisfaction or feature usage. Qualitative responses require thematic analysis to identify common issues or suggestions. For example, a university’s e-learning platform survey might reveal consistent complaints about slow page loading, prompting performance optimization.
Form builders are software tools that enable the creation of customized digital forms to collect user feedback efficiently. These tools are integral to modern software support frameworks, allowing developers and support teams to design feedback forms without extensive coding. In Kenya, form builders support user engagement across sectors including healthcare and cooperative societies, where tailored feedback collection is critical.
Form builders offer drag-and-drop interfaces, templates, and integration capabilities that simplify feedback form creation and deployment. They enable collecting structured data such as user details, feedback categories, and ratings with validation rules to ensure data quality. For example, a hospital using a patient management system may deploy forms to capture user-reported software issues categorized by urgency and type, improving support response.
Several form builders have gained traction in Kenya due to their ease of use and affordability. Google Forms is widely used for its accessibility and integration with Google Workspace, while Typeform offers interactive and user-friendly forms that enhance user engagement. Microsoft Forms integrates well with Office 365 environments common in county government offices, facilitating seamless feedback collection from staff using internal applications.
Effective feedback forms must balance comprehensiveness with user convenience. Developers should design forms that capture key information such as user identity, issue description, and satisfaction ratings while minimizing completion time. Utilizing conditional logic to show or hide questions based on previous answers can streamline the process. For instance, a cooperative society might design a form that asks additional details only if users report transaction failures in their mobile banking app.
Integrating form builders with helpdesk or issue tracking systems enhances the feedback management process. Automated workflows can route form submissions to appropriate support teams, trigger notifications, and update ticket statuses. For example, a software development firm supporting a retail chain’s inventory system might link Google Forms submissions directly to a Jira project board, ensuring swift issue resolution and data-driven support decisions.
This chapter explores effective methods for gathering user feedback, which is essential for improving end-user support services. It begins by discussing various activities involved in obtaining feedback, emphasizing the importance of engaging users to understand their experiences and needs. The chapter then delves into the use of surveys as a structured approach to collect quantitative and qualitative data from users, highlighting their role in identifying areas for improvement. Additionally, it covers project work that involves designing and implementing feedback mechanisms tailored to specific user groups or organizational contexts. The chapter concludes with an examination of form builders, tools that facilitate the creation of customized feedback forms to streamline data collection and analysis. Together, these methods provide a comprehensive framework for gathering actionable user insights to enhance support services.
Question 1 key points:
Question 2 key points:
The Nairobi-based software firm M-TIBA recently launched a new health management system targeted at county hospitals. After initial deployment, the company decided to gather user feedback to improve the system.
Tasks:
a) Design a survey outline that M-TIBA could use to gather feedback from hospital staff using the system. (5 marks)
b) Recommend two form builder tools suitable for creating and distributing this survey in a Kenyan healthcare context and justify your choices. (4 marks)
c) Explain how M-TIBA should analyze the collected feedback to inform the next development cycle. (6 marks)
a) The survey outline should include sections on system usability, feature usefulness, error reporting, and general satisfaction. Questions should be a mix of closed-ended (e.g., Likert scale ratings) and open-ended for detailed comments. Demographic questions to segment responses by role (nurse, doctor, admin) are important.
b) Recommended tools could include Google Forms for its accessibility and integration with Google Workspace widely used in Kenyan institutions, and KoboToolbox, which supports offline data collection useful in hospitals with intermittent internet. Both tools offer ease of use and reliable data export options.
c) M-TIBA should first clean and categorize feedback data, quantifying ratings and coding qualitative comments for themes. Prioritization of issues should consider frequency and severity of reported problems. This analysis will guide developers on critical fixes and feature enhancements, ensuring the next release addresses actual user needs effectively.
Question 11 (Compulsory - 20 marks)
At the National Hospital Insurance Fund (NHIF), the IT department has just launched a web portal for members to submit claims online. Initial uptake has been low and users report difficulties navigating the system. As the software developer tasked with improving the portal:
a) Design a survey using an online form builder to gather detailed user feedback on the portal’s usability. Include at least five question types and justify their inclusion. (10 marks)
b) Explain how you would integrate project work activities with this survey to ensure continuous improvement of the portal. (10 marks)
Question 12 (20 marks)
Discuss the role of form builders in enhancing the efficiency and accuracy of user feedback collection in software development projects at county government offices. Include examples of how form builders can be customized to meet diverse user needs.
Question 13 (20 marks)
Explain the process and key considerations for analyzing survey data collected from end-users of a new software application deployed by the Kenya Revenue Authority (KRA). How can this analysis influence future software updates?
Question 14 (20 marks)
Evaluate the benefits and limitations of using surveys as a method for gathering user feedback in the development and support of educational software at public universities in Kenya. Suggest alternative or complementary methods that could be employed.
Question 11
a) The survey should include closed-ended questions (e.g., multiple choice) to quantify common issues, Likert scale questions to measure satisfaction levels, open-ended questions for detailed user suggestions, demographic questions to segment users, and ranking questions to prioritize features. This mix ensures quantitative data for analysis and qualitative insights for context.
b) Project work can involve iterative cycles where survey results inform development sprints. Users engaged in project activities can test new features and provide ongoing feedback, creating a feedback loop that enhances responsiveness and user-centered design.
Question 12
Form builders streamline feedback collection by offering customizable templates, conditional logic to tailor questions based on prior answers, and integration with databases for real-time data management. For example, county offices can customize forms to capture specific departmental feedback or language preferences, improving response quality and relevance.
Question 13
Analyzing survey data involves data cleaning, coding open-ended responses, statistical analysis for trends, and cross-tabulation by user demographics. Considerations include ensuring data validity, avoiding bias, and protecting confidentiality. The insights guide prioritization of bug fixes, feature enhancements, and user training programs in subsequent software updates.
Question 14
Surveys provide structured feedback and are cost-effective for large user groups, but may suffer from low response rates and limited depth. Limitations include potential misinterpretation of questions and lack of interactive follow-up. Complementary methods like focus groups, interviews, or usability testing provide richer qualitative data and validate survey findings.
Time: 2 Hours | Type: Individual
Resources Required:
You are tasked with supporting user feedback collection at the Nairobi County Government ICT department, which is developing a public service delivery mobile app.
Tasks:
i. Open Google Forms and create a new survey form titled "Public Service App User Feedback".
ii. Add at least five questions including multiple choice, rating scale, and open-ended types relevant to app usability.
iii. Configure the form to collect respondent email addresses and limit to one response per user.
iv. Share the generated survey link and record the URL for distribution.
Assessor Observation Criteria:
Time: 1.5 Hours | Type: Individual
Resources Required:
At a Kisumu software startup developing an e-commerce platform, you have been requested to build a reusable feedback survey template for end-user testing phases.
Tasks:
i. Log into Microsoft Forms and start a new blank form titled "E-commerce Platform User Feedback".
ii. Insert at least six relevant questions including Likert scale and dropdown menu types.
iii. Add a section description explaining the purpose of the survey.
iv. Save the form as a template for reuse in future projects.
Assessor Observation Criteria:
Time: 1 Hour | Type: Individual
Resources Required:
You are supporting the KNH software development team by analyzing user feedback collected via Google Forms for their patient management system.
Tasks:
i. Import the provided CSV file into Excel and clean any inconsistent data entries.
ii. Create a pivot table summarizing user ratings for system usability.
iii. Generate a bar chart visualizing the frequency of common user complaints.
iv. Save the Excel workbook with analysis and charts.
Assessor Observation Criteria:
Time: 2 Hours | Type: Individual
Resources Required:
A fintech company in Mombasa requires a customized feedback form for their mobile banking app users to report issues and suggest features.
Tasks:
i. Log into JotForm and create a new form titled "Mobile Banking App Feedback".
ii. Add fields for user contact details, issue description, and feature requests with conditional logic.
iii. Customize the form appearance to match the company’s brand colors.
iv. Test the form by submitting a sample feedback entry.
Assessor Observation Criteria:
Time: 3 Hours | Type: Individual
Resources Required:
At a software development firm in Eldoret, you have been assigned to integrate user feedback surveys into an existing web application for continuous improvement.
Tasks:
i. Clone the provided web app repository and open it in Visual Studio Code.
ii. Using the SurveyMonkey API, embed a feedback survey form into the app’s user dashboard.
iii. Ensure the survey form submits data asynchronously without page reload.
iv. Commit and push changes back to the repository with descriptive commit messages.
Assessor Observation Criteria:
Time: 2.5 Hours | Type: Individual
Resources Required:
The Nakuru Agricultural Cooperative requires a mobile-friendly feedback form within their app to collect farmer input on software usability.
Tasks:
i. Create a new canvas app in Power Apps focused on feedback collection.
ii. Design a form with input fields for text, rating, and image upload.
iii. Connect the form to a SharePoint list to store submitted feedback.
iv. Test the app on a mobile emulator and verify data storage.
Assessor Observation Criteria:
Time: 2 Hours | Type: Individual
Resources Required:
You are supporting a Turkana county health project where internet connectivity is unreliable; offline feedback form collection is needed for community health workers.
Tasks:
i. Create a feedback form in KoboToolbox with fields for user demographics and service satisfaction.
ii. Download the form for offline use on an Android device.
iii. Simulate data entry offline and upload the data when connected.
iv. Export collected data to Excel for analysis.
Assessor Observation Criteria:
Time: 1.5 Hours | Type: Individual
Resources Required:
An insurance firm in Nairobi wants a feedback survey that adapts questions based on prior user responses to improve data relevance.
Tasks:
i. Create a new survey form and enter base questions.
ii. Configure branching logic so that certain questions appear only if specific answers are chosen.
iii. Test the form to verify correct branching paths.
iv. Share the form link and document the branching setup.
Assessor Observation Criteria:
Time: 1 Hour | Type: Individual
Resources Required:
You are assisting Kisii county education officers by transferring a feedback survey template from Google Forms to Microsoft Forms for better integration with their existing systems.
Tasks:
i. Export the Google Forms survey template questions and structure manually or using available tools.
ii. Recreate the survey in Microsoft Forms matching question types and order.
iii. Compare both forms for consistency and make necessary adjustments.
iv. Save and share the Microsoft Forms survey link.
Assessor Observation Criteria:
Time: 2 Hours | Type: Individual
Resources Required:
A software company in Thika wants their user feedback form embedded in their website to reflect corporate branding through customized appearance.
Tasks:
i. Open the provided HTML feedback form code in the editor.
ii. Create and link a CSS stylesheet to style form elements including fonts, colors, and spacing.
iii. Ensure the form is responsive and visually consistent across devices.
iv. Preview and save the updated web form files.
Assessor Observation Criteria:
Time: 2 Hours | Type: Individual
Resources Required:
An NGO in Nairobi requires a feedback form that supports English and Swahili to cater for diverse community users.
Tasks:
i. Design a feedback form with questions in English.
ii. Duplicate the form or use multilingual features to add Swahili versions of each question.
iii. Configure the form to allow users to select their preferred language.
iv. Test form functionality in both languages and document the process.
Assessor Observation Criteria:
Time: 1 Hour | Type: Group of 2
Resources Required:
A retail software company in Nakuru wants to collect user feedback by sharing survey links through WhatsApp groups.
Tasks:
i. Prepare the survey form link on a laptop.
ii. Create a WhatsApp broadcast list or group including sample user contacts.
iii. Send the survey link with a concise message requesting feedback.
iv. Monitor and record user responses received within a specified timeframe.
Assessor Observation Criteria:
At the start of this chapter we promised you would be able to:
Tick each one you can genuinely do.
So, are you there yet?
You're competent when you can confidently do 50% or more of what this chapter promised.
Sign in to record how you're doing.