He was in charge of travel services and eventually engaged in organizational development as an engineering manager. In 2020, Taka joined WealthPark because he shared the company's mission to bring investment opportunities in alternative assets to everyone. In April, he became VP of Engineering, leading an international engineering team of more than 40 members from over 10 countries. Takahiro Fujii, VPoE About us
Coach, Trainer and facilitator, passionate about Complexity Science and human system dynamics. During his career he has worked in a wide range of fields: from code development to user experience, product and business development, digital transformation and HR. He has coached teams, Scrum Masters, Product Owners, Executives and C- level Leaders in different business contexts such as IT, advertising, banking and TELCO.
About 20% are offshore, or always work remotely 40+ Engineering organization FrontEnd, BackEnd, EM, Mobile, QA, Agile Coach, Security, SRE etc Tech focused (Go, React, Ruby, DevOps, etc.) Changing from Business Driven to Product Driven Small cross functional teams able to develop independently and fast(Squad, inspired by Spotify model) About the organization
my very favorite habits is that usually around 3:00 PM, a "Coffee ☕️?" to the engineering channel on Slack. We all go for a walk to the nearby Family Mart, buy coffee, and talk about it on the way office. Not all of us go, but those who want to and those who can go. Coffee Culture at WealthPark
moving to remote work. You can report via text or MTG, but you can't have interactive discussions. You can't put up stickies and make kanban. We were very fortunate to have online whiteboards such as Miro, Figjam, Strap, etc. that we could use without stress. (If you're not using them, I don't think you have a choice not to.) Without Miro we could not survive
continued through VS Code Live Share and Code with me (Jetbrains). These have been around as concepts for a long time, but it is only relatively recently that they have become available for use on a practical level. It was really good. Live share supports pair and mob programming
complement the missing parts, but this is not true. The result is often just MTGs with no active discussion and more uninspiring huddles. A : "I did A,B,C." B : "I did C,D. So far it's good. C : "I did E." Facilitator : "Something to discuss or talk?" A&B&C : "No." About meetings & communication
increased. While this is a good thing, it can be very difficult to find the information you need, or find it again, if there is a discussion on Slack that you need to look back on later, or if you are not sure how to use the slack channels. Covid # of slack messages at WealthPark
facial expressions and emotions it's something that comes easy and natural in a physical environment. In a remote setting we suffer this lack of "presence" (turned off cameras, split screens, small screens).
mood in a room we not only need to read facial expressions but also body language. Interacting with people without having access to their body language it's an huge cognitive load for our brains.
calls > Slack messages Visualize with collaborative tools Express your emotions as much as possible Pair work sessions Camera on Record short videos for a better async communication Proper onboarding new members
a place to tweet, not report. (If you like Twitter, you know what I mean.) If you mumble, others will help you (sometimes). This feeling can make helping each other less stressful. Note : Some people don't like Twitter.
closely on an ongoing basis..." "Oh, I see. I didn't notice, but I'm glad you're watching.." Boss Member ”I've been following your work closely on an ongoing basis..." "No, no, no, you never see it, and you don't know what kind of code I'm modifying." Before
and feedback Seems low for the market value. Feel uneasy about relative evaluations (not know what other people's evaluations are) Not satisfied with the feedback I receive. From there, the criteria can be clarified, and the content and duration of the feedback can be changed.
own, but be able to consult and report easily. Don't make assumptions. If you have an assumption, make it known in the conversation ("I was wondering if this might be the case...") - this doesn't mean don't make a decision. Be honest about what I don't know. Kudos Support in non- technical matters as a company
gather context Gemba "walk" is not possible, but shadowing meetings helps a lot Missing the "watercooler" conversations full of insights Build and gather trust, then focus on processes
of human nature) Ask help without hesitation Give feedbacks, ask for feedbacks Clarify roles and responsibilites Keep expectations real Practice active listening "Start with why" Acknowledge others for their good work Be transparent and genuine Talk about yourself