The front page for the Digital team
The Blog is the place to go for the latest developments in Digital. As an open forum, anyone is free to post to the blog using some simple instructions.
- 2023 Second Quarter Knowledge Base Analytics
- Deconstructing identities
- What’s changing
Brittany McNamara - 2023-06-30 00:00:00 +0000 UTC
After an unusual busy first quarter, traffic levels out in Q2. Traffic to the Knowledge Base is still up compared to this time last year, but down compared to last quarter’s high amount of users. While we published a few net new docs, nothing affected all Banno institutions this quarter like it did in Q1.
2023 First Quarter Knowledge Base AnalyticsBrittany McNamara - 2023-06-28 00:00:00 +0000 UTC
We’re off to great start in 2023 with traffic up 51.3% percent from the start of 2022! It was a busy first quarter with customers wanting information on transaction enrichment, UI changes to the Online and Mobile login screen (sign in with a passkey), AND Finicity’s third-party account aggregation. With those docs published on the Knowledge Base, it is more than the usual number of eyes and clicks.
April 2023 S/O Analytics UpdateBrittany McNamara - 2023-05-13 00:00:00 +0000 UTC
We now have a solid four months of consistent engagement on S/O to work with! We’ve observed, analyzed, and discussed how things are going on S/O. As a doc team, we’ll be honest and share that adding content to the Knowledge Base from S/O has been juggled with other priorities and put lower on the to-list. That is about to change. May’s report will soon be in the works, but starting in June we’re focusing more on the backlog of content that we can publish on the Knowledge Base. We plan to make strides over the summer months by first adding content around trending questions and tags.
March 2023 S/O Analytics UpdateBrittany McNamara - 2023-05-12 00:00:00 +0000 UTC
We’ll keep this intro short and sweet, again. Overall, engagement on S/O for the month of March was down slightly from February. We’ll see how things shake out for April! Pressed for time? We suggest reading April’s update as that gives you the latest trends and observations.
February 2023 S/O Analytics UpdateBrittany McNamara - 2023-05-11 00:00:00 +0000 UTC
We’ll keep this intro short and sweet. As the year progresses, our observations will deepen as we gauge the various analytics. Feel free to check out updates for March and April, too! Pressed for time? We suggest reading April’s update as that gives you the latest comparisons.
January 2023 S/O Analytics UpdateBrittany McNamara - 2023-05-10 00:00:00 +0000 UTC
For everyone clamoring to know our organization’s engagement in Stack/Overflow, the numbers are in! Well, they’ve always been in but we finally have a stock of monthly analytics ready to share. While we began using S/O in October 2022, we’re providing updates starting January 2023. We believe this starting point gives us an accurate representation of how our organization uses S/O month to month. Contributors and SMEs should have felt comfortable using S/O and become familiar with the process.
TL;DR Pressed for time? We suggest reading April’s update as that gives you the latest comparisons.
2022 Knowledge Base Analytics in Review & the Road AheadBrittany McNamara - 2023-05-08 00:00:00 +0000 UTC
2022 was a second straight year of significant growth. Compared to 2021, we saw nearly a 40% rise in users! Starting in February 2022, we had 4,000+ users visit the Knowledge Base each month—January 2022 was close with 3,896 users. We attribute this growth not only to the increasing number of customers, but the Knowledge Base’s expanded visibility with customers.
2022 Fourth Quarter Knowledge Base AnalyticsBrittany McNamara - 2023-05-07 00:00:00 +0000 UTC
We ended the year with a bang—traffic is up from last quarter and we saw the most number of visitors in a single quarter. Read on for more, and check out 2022 in review!
Introducing the "Refreshed" Knowledge Base & 2022 Third Quarter AnalyticsBrittany McNamara - 2022-11-15 00:00:00 +0000 UTC
By the time we share this third quarter report, you may have noticed a different “look” for the Knowledge Base! In keeping up with the Jack Henry rebrand, we updated the site’s aesthetics for a fresher and more modern feel. We hope you like it as much as we do! More exciting changes will be on the way with redesigning the site architecture and homepage. Stay tuned!
Going forward with our reports, we’re beginning to focus on how users access the Knowledge Base, understand user behavior, and share more of the top visited pages. This will help us hone in on building out specific topics. We’re also sharing more details on how the Knowledge Base grows from year-to-year and quarter-to-quarter. It’s rewarding to see how much user activity has increased since we first started using Google Analytics!
2022 Second Quarter Knowledge Base AnalyticsBrittany McNamara - 2022-07-07 00:00:00 +0000 UTC
As we reflect on the second quarter, here are a few noteworthy comments.
2022 First Quarter Knowledge Base AnalyticsBrittany McNamara - 2022-04-08 00:00:00 +0000 UTC
From the first of the year through March, the number of users visiting the Knowledge Base increased by 14.4%! As part of our efforts to assist financial employees and promote documentation, the monthly Banno Statement now includes a section dedicated to featuring docs. Since January, the monthly statement has been highlighting documentation for both new features and previously released features that hadn’t yet been covered. We see our efforts paying off!
2021 Knowledge Base Analytics in ReviewBrittany McNamara - 2022-01-27 00:00:00 +0000 UTC
2021 Year in Review (with a bit of 2020 and 2022 thrown in)
With 2021 already in the rearview mirror, 2022 is full steam ahead! At the close of the year, the documentation team officially celebrated its first full calendar year using Google Analytics to gauge user interaction on the Knowledge Base. You might not have known that we track the site, so here are some insightful stats wrapped up in a 2021 review and where the site’s currently sitting.
Improving Documentation SystemDave Johnson - 2021-10-05 00:00:00 +0000 UTC We’re forming a new working group to improve our written culture and our documentation system. The intention of this group is to address a long-standing and significant piece of organizational debt we all struggle with everyday: Knowing what should be written down Where it should be stored How to keep it current How do we find information The ideal working group size is no more than 5 people, but because this initiative spans the entire Banno organization, we have a slightly larger group with someone from every team (Analysts, Design, Engineering, Infra, IS, Product, and Support/Ops). Digital Infrastructure
Eli Barb - 2021-05-05 00:00:00 +0000 UTC
TL;DR
Many of us have been thinking about our identity, reflecting on the joining together of Banno, Bolts, Geezeo, and Internet Solutions over a year ago into a new Digital group. Who are we now and who will we be? We’ve undergone a year of truly massive change, uncertainty, and discovery. You may be reflecting on the past and even starting to dream about what the future may hold for our teams.
As a group of ~600 individuals we’re stretched to the limit trying to maintain close bonds in our new larger community. How do we continue to transform, to innovate, to improve? How can we ensure some measure of independence to allow for progress, while fostering a humble union that moves in step together? We are a complex body of individual parts!
…
Product Questions in SlackChad Killingsworth - 2021-04-21 00:00:00 +0000 UTC
Over the last several years, Banno has seen tremendous growth both organizationally and in the number of features in our apps. This growth has led to a similar growth in the number of questions being asked in various slack channels about how our product functions in specific scenarios or why something was designed a specific way. These questions have been growing in number directly to our engineering teams which can often lead to a significant amount of research required from engineers. Engineering teams often answer a question as precisely as possible, but that level of specificity is rarely what we want to communicate externally.
To help optimize this experience and ensure we are documenting correct questions, we are moving all product questions to the #org-prod-mgmt channel. There the product team will help triage these questions appropriately. If a question requires engineering or analyst research, the product team will reach out to the engineering team and/or analysts and facilitate this research.
…
Documentation Update December 10, 2020Wes Iliff - 2020-12-11 00:00:00 +0000 UTC
Happy holidays, everyone! I know what you all wanted: one last documentation update to wrap up the year. And who are we to say no? We made some pretty cool changes to the Knowledge Base recently, so let’s dive right in.
Documentation Update November 9, 2020Wes Iliff - 2020-11-09 00:00:00 +0000 UTC
Happy November, y’all! The days are getting shorter, but the doc train keeps on a-rollin’! We’ve got a lot of new docs, and a little bit of new process, so let’s dive in!
Documentation Update September 29, 2020Wes Iliff - 2020-09-29 00:00:00 +0000 UTC
Hey folks,
Another month, another documentation update! It’s been a little less than a month, and each member of the team has lost a bit of time during September, so this update might be a little shorter than usual, but we’ve still got plenty of cool stuff that’s shipped!
Documentation Update September 4, 2020Wes Iliff - 2020-09-04 00:00:00 +0000 UTC
Happy September, y’all! The team saw a bout of illness that set us back a bit this month, but we’re caught up and getting back ahead of the game, so let’s go with another Documentation Update!
Documentation Update August 3, 2020Wes Iliff - 2020-08-03 00:00:00 +0000 UTC
Hey all!
It’s been a minute or two! A lot has changed since the last documentation update, so let’s dive right in!
Diversity, Equity, and Inclusion Slack ChannelBritany Meadows - 2020-06-03 00:00:00 +0000 UTC
Conversation Space
A new Slack channel was created today: #org-diversity-equity-inclusion. I shared this in #team-banno but was rightfully held accountable that I needed to share this in an email so it can be communicated out to everyone without getting lost in the normal Slack channel shuffle.
PagerDuty UpdatesEli Barb - 2020-06-02 00:00:00 +0000 UTC
Upgrades!!! whut whut
In the last few months we’ve upgraded our license level within PagerDuty. With this new tier we have access to enabling a few new features. Read further for the changes you can expect.
Cross Organizational CollaborationEli Barb - 2020-05-20 00:00:00 +0000 UTC
Digital Group Tools
Increasingly our teams are working together across organizational boundaries; Geezeo, NetTeller, Bolts and Banno. Each of these groups has a slightly different approach to communication and collaboration. We’ve been receiving questions about calendar visibility or access to documents stored across organizations, as well as the future of some of these tools. To help bridge the gap we’ve put together a few details to help guide our cross-organization work.
Slack integrates with Microsoft TeamsEli Barb - 2020-04-21 00:00:00 +0000 UTC tl;dr /teams-call meeting Slack has a new Microsoft Teams call integration. It gives us another audio/video option for collaboration with an individual or with your team and it’s really easy to use. It is particularly helpful if you need to work with someone that doesn’t have Slack, Zoom, or Hangouts access. (Most of Jack Henry). Enjoy this brief tutorial video and please excuse the corny dialogue. Documentation Update March 9, 2020
Wes Iliff - 2020-03-09 00:00:00 +0000 UTC Time for another documentation update, and this one’s a doozy. You know that cool Banno Knowledge base, located at knowledge.banno.com, filled with all kinds of useful technical docs for our customers? Wait, that URL seems wrong. And why don’t I have to auth for it? Oh yeah, that’s the public one. It’s live now and you can use it and share it and love it. BUT BUT BUT before you do, please read the two paragraphs below. Banno Knowledge Name Change
Wes Iliff - 2020-03-06 00:00:00 +0000 UTC If you’ve tried to go to <docs.banno.com/help> today, you might have noticed it’s not there any more. This is by design, not accident! As we prepare the site to go live, it’s undergone a name change, as the help site is now officially known as Banno Knowledge. To facilitate taking the public version live, we’ve changed the repository name as well. As such, the github repo can now be found at https://github. Documentation Update Feb 20, 2020
Wes Iliff - 2020-02-20 00:00:00 +0000 UTC Hey folks, Wanted to give an in-depth update on the current state of our documentation efforts, especially when it comes to the Banno Knowledge Base. There’s a lot to share, so I’ll do my best to keep this readable. Banno Knowledge Let’s start with the easy one: we’ve had a ton of names for this help site. Now we have one: the Banno Knowledge Base, or Banno Knowledge for short. Banno Knowledge is how we will communicate about this product to customers, and it’s where we will direct people with questions. New Working Group: API Design Language
Janene Pappas - 2020-01-27 00:00:00 +0000 UTC New Working Group: API Design Language We have a large set of API docs across nearly all of our API endpoints. Due to the length of time that we’ve been writing these docs, number of different teams touching those docs, even the opinions of individual contributors, all with very little written standards, it’s amazing how cohesive the API docs are at this point. We are spinning up a working group to help design an API “Design Language”. Banno Tracing 01/15/2020
Calvin Brown - 2020-01-15 00:00:00 +0000 UTC Banno Tracing Hey all! I wanted to write a up something on what dreamwork has been working on in regards to tracing. If you don’t know what tracing is, there are some good resources out there https://opentracing.io/docs/overview/what-is-tracing/ https://www.jaegertracing.io/docs/1.14/ We are using https://github.com/Banno/tracenium/ for the tracing setup and propagation of the trace headers. Currently only applications that live in Azure (K8’s) are able to report spans to the Jaeger agent. We used our ingress for push-registrations to test out tracing. Leadership Retro Notes 12/13/19
Wes Iliff - 2019-12-19 00:00:00 +0000 UTC tl;dr Discussed top-down leadership decisions Discussed how hero culture affects those decisions Full Notes This week was basically one long discussion topic. There will be more written artifacts coming out of this discussion, but for now, let’s dive into what we have! The agenda item that spawned the discussion was an incident wherein leadership got involved with an engineering decision and team members felt there was no option to push back on the decisions made. The Happiness Door Update
Wes Iliff - 2019-12-09 00:00:00 +0000 UTC
The Happiness Door is dead! Long live The Happiness Door!
After gathering a large amount of feedback over how The Happiness Door works, we’ve made a few changes to the form. The details on how it works can be found in the above blog post, but if you’d like to know more about the feedback we received and how we decided on the current format, read on!
Github Authentication Changes - Don’t Lose Your Access!Chad Killingsworth - 2019-08-27 00:00:00 +0000 UTC
Do this right away
We are enabling single sign on integration to GitHub using your Jack Henry credentials. To enable, you only need to visit https://github.com/orgs/Banno/sso and link your Jack Henry account to your GitHub account. You’ll then log in to the Jack Henry portal using your @jhacorp.com username and your JHA password. You must do this before September 15 or you will lose access to the Banno organization on GitHub.
Wellness Credit Health ScreeningsWes Iliff - 2019-08-26 00:00:00 +0000 UTC As many of you have seen, the Wellness Credit for 2020 requires a biometric screening for both associates and any spouse/domestic partners who qualify. For those who did not receive this communication, a PDF with most of the following information can be found on Sharepoint. As there have been concerns about how to get these screenings, we’re running down the steps here for those who need some guidance in completing these screenings and getting their 2020 credit. How to make a blog post
- The Banno blog is an open forum for any team member to post important updates that the team should know about. Making a post is easy: simply create a new markdown file with a YYYY-mm-dd date at the beginning of the title in the /_posts folder of the Wiki GitHub repo, as outlined in Jekyll’s documentation. To populate our list of blog posts correctly, be sure to include the following items in the front matter at the top of your file: