UAT SurveyYour feedback will help improve the final product. Thank you!Please enable JavaScript in your browser to complete this form.Name *FirstLastEmail *Name of school *What is your role? *Help desk / service deskSystems administrationIT management / leadershipOtherHow long have you worked in higher-ed IT? *Less than 1 year1-3 years4-7 years8-15 years16+ yearsWhat type of institution do yo work at? *Private college/universityPublic universityCommunity collegeTechnical/vocational institutionOtherApproximately how many faculty does your team support? Selected Value: 0 Approximately how many staff does your team support? Selected Value: 0 Important support context is often fragmented across multiple places. *Strongly disagreeDisagreeNeutralAgreeStrongly AgreeMy team relies too much on informal knowledge or memory. *Strongly disagreeDisagreeNeutralAgreeStrongly AgreeMissing context regularly slows down support work. *Strongly disagreeDisagreeNeutralAgreeStrongly AgreeKnowledge transfer is difficult when staff change roles or leave. *Strongly disagreeDisagreeNeutralAgreeStrongly AgreeCurrent systems do not adequately capture the people-centered context that helps us provide better support. *Strongly disagreeDisagreeNeutralAgreeStrongly AgreeIt is hard for newer team members to access the same knowledge that experienced staff have. *Strongly disagreeDisagreeNeutralAgreeStrongly AgreeWhich sources do you currently rely on for this type of knowledge? Select all that apply. *Ticketing systemEmailShared documentsPersonal notesInternal wiki/knowledge baseChat/messagesOther staff membersCRM or directory-like systemOtherProduct concept *A tool like this could improve support continuity.A tool like this could help preserve institutional knowledge.A tool like this could help newer staff ramp up faster.A tool like this could fit into our team’s workflow.A tool like this would offer meaningful value beyond our current tools.None of the above.Imagine a tool designed for IT staff at post-secondary institutions that helps teams maintain useful profiles and support-related context about faculty and staff, so knowledge is easier to preserve, retrieve, and use across the team.Which potential benefit is most compelling? *Faster access to useful contextBetter knowledge retentionBetter onboarding for new staffMore consistent support across the teamLess dependence on tribal knowledgeNone of the above.Which concern(s) would you have about a tool like this? *Too much effort to keep updatedPrivacy or sensitivity concernsUnclear ownership/governanceToo similar to tools we already haveLow adoption by staffBudget concernsNone of the above.How likely would you be to use a tool like this if it were available? *Very unlikelyUnlikelyNeutralLikelyVery likely Which Which institution How likely would you be to recommend piloting a tool like this on your team? *Very unlikelyUnlikelyNeutralLikelyVery likelyWhich users at your institution would benefit most? *Who would most likely own the budget or decision for a tool like this? *IT directorCIO / CTODepartmental IT leadershipOperations / administrationNot sureOtherWhat kind of evidence would you need before recommending purchase? *Clear time savingsBetter onboarding outcomesBetter continuity when staff changeImproved support consistencyStrong security/governance controlsUser adoption evidenceOtherWhat annual price range feels plausible for a tool solving this problem at your institution? *Under $2,500$2,500–$5,000$5,001–$10,000$10,001–$25,000Over $25,000Not sureWe would not pay for thisAny additional comments?Submit