Salesforce for Higher Ed combines the Salesforce Lightning Experience with HEDA (Higher Ed Data Architecture), providing a cloud platform supporting student management and engagement, admissions and academics, and other higher ed administrative support functions.
N/A
Taskstream-Tk20 (discontinued)
Score 6.0 out of 10
N/A
Taskstream-Tk20 is software for higher education institutions, that is now discontinued. It was designed to help users manage institutional effectiveness (accreditation, strategic planning & budgeting, assessment planning, program review, faculty credentialing, reporting & analytics), monitor and improve program quality (student management, clinical & field placements, course evaluations, surveys, ePortfolios), and assess student learning and track progress (outcomes assessment, course-embedded…
It is most suited for those within the education industry. For students and staff in particular, the Education Cloud allows seamless connectivity between each person and helps students stay on task. It can be very overwhelming as a student to have so many responsibilities in different areas, so Salesforce does a great job of offering many features that ease this process.
TS is well suited as an eportfolio system when documents need to be archived for accreditation or long term assessment profiles. It would not be suited for routine classroom assessment or daily integration into a mobile or online platform. It is also not suited for non-technology oriented students, faculty, or staff. The user needs some level of confidence when using TS
Students can be searched via department or program so that I can search for a specific student. I can scroll through all students and find the one I need to evaluate or I can choose the option to "show all work waiting evaluation" and it will bring up student submissions that I have waiting for me.
TaskStream easily links or embeds into online classroom portals. We use BlackBoard now and students have an ePortfolio link that takes them directly to their menu of student instructions etc.
TaskStream actually serves its purpose well of archiving portfolio assignments so they can be referenced for an individual reason or for accreditation or reporting. It accomplishes this important goal for educational institutions.
It’s hard to run reports or create working “views” for Enrollment/Student Advisor teams that include both Leads and Contacts in the same report.
Some fields do not map from Lead to Contact object. When a student transitions from application to acceptance, some dropdown and fill-in fields completely disappear from the student’s page in Salesforce. Every version of Salesforce I’ve used has this problem.
Salesforce overall is clunky and confusing for the average user. We require thorough Salesforce training for new hires on all teams because it’s not user-friendly or obvious what to click on to achieve a specific task.
There is a steep learning curve with TaskStream as the searching and even evaluating process is not intuitive. Although it is visual like a flowchart or grid--which I think is an asset--sometimes I can lock others out of the document or I have choices of "returning to student and deleting all instances of this submission" or "returning to student later" or "returning to student now and not deleting this submission" . . . I am unsure what these different options MEAN to the programmer. What I think they mean has not always proved to be correct. As a result, it creates confusion or frustration in the process.
The way TaskStream is used in the education department, multiple people may evaluate a capstone project in order to verify approval to progress to the next step--or next capstone activity. If a faculty or staff user inappropriately marks a document inside TaskStream, it can undo the submissions and make the process begin all over again. I have had this happen accidentally--a colleague returned a document the wrong way. The student then had to resubmit, two other colleagues had to approve indvidually, and then the 3rd party had to approve it the correct way. So although some aspects or tools/buttons in TS may not be intuitive, making errors in process can be time-consuming and create frustrations as they affect other people's work as well.
TaskStream does not work on a mobile device very efficiently. Because it has pop up windows, I often cannot get it to cooperate on a tablet, ipad, or mobile device. This is problematic when I am travelling and need to attend to a document in TS.
People will respond on time even though Salesforce is such a large organization. This also includes various methods of getting support beyond just calling - they have dedicated reps, chat, chatter, etc that all make the experience more pleasant.
I have not used similar products and I am new to this role. Salesforce has been very easy to learn and I appreciate the support and ability to access the platform when I need to. I was able to easily learn the program and become skilled in what I needed to do. It also made the transition to digital forms quite easy
TS is the only e-portfolio system I have used for students. I have used Kenobi as a wiki for holding data that was interactive with other faculty members. I found it to be simple but lacking in ability to be robust or host dynamic data. Kenobi does not have the ability to score or complete rubrics in the same fashion--there is a place for rubrics, but it is not as dynamic as TS
Positive: Our entire company is more aligned because while still complying with FERPA, the right people have access to student records while also having the correct permissions.
Positive: we can integrate with our partners who also use Salesforce, while still complying with FERPA.
Negative: we've needed to hire a Salesforce Development team with multiple people to accurately customize the tool to work for us.
Although I am not on the administrative side of my department, it has been and continues to be the e-portfolio management system of choice for Walden University. Walden is now a for-profit school that is trading on the market. With that in mind, they would not invest in a system that was not functioning to its expectations.
If you view TS from a faculty or user perspective, I have colleagues who are frustrated with TS and its not "intuitive" nature, and they have eventually quit working for Walden and TS and the multiple systems we have to use was cited as a reason.
it would be ideal if there was one overall system that could manage all the different data artifacts we have to collect as faculty in higher ed. Due to accreditation and liability standards, we have to maintain faculty quality, classroom quality, student-learning quality and many other aspects of the educational system. TS is ONE of the systems we use. In the perfect world, there would be just one or two that completed the job.
